linux-kernel - Re: [PATCH] Add MCE support to KVM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <49EC3198.9070902@redhat.com>
Date:	Mon, 20 Apr 2009 11:26:00 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Gerd Hoffmann <kraxel@...hat.com>
CC:	Anthony Liguori <anthony@...emonkey.ws>,
	Huang Ying <ying.huang@...el.com>,
	"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCH] Add MCE support to KVM

Gerd Hoffmann wrote:
>> Right now everything in the vcpu is emulated in the kernel. Everything
>> else is emulated either in the kernel (irqchip) or in userspace. This
>> makes things easier to understand, and is more future friendly if more
>> cpu features become virtualized by hardware.
>>
>> While these are not compelling reasons, they at least lean the balance
>> in favour of a kernel implementation.
>
> The xen pv-on-hvm drivers use an msr to indicate "please place the 
> hypercall page here".  Handling that in kernel isn't an option IMHO.

The contents of the hypercall page are vendor specific.  This can be 
handled from userspace (though ideally we'd abstract the cpu vendor 
away).  The Hyper-V hypercall page is more problematic, as it's 
specified to be an overlay; the page doesn't have to exist in guest RAM.

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/