| 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
| ||
|
Message-ID: <20121012142204.47b9d780@mantra.us.oracle.com> Date: Fri, 12 Oct 2012 14:22:04 -0700 From: Mukesh Rathor <mukesh.rathor@...cle.com> To: Ian Campbell <Ian.Campbell@...rix.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>, "Xen-devel@...ts.xensource.com" <Xen-devel@...ts.xensource.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [Xen-devel] [PATCH V2 1/7]: PVH: basic and header changes, elfnote changes, ... On Fri, 12 Oct 2012 09:48:48 +0100 Ian Campbell <Ian.Campbell@...rix.com> wrote: > > index fdce49c..9323b8c 100644 > > --- a/arch/x86/xen/Kconfig > > +++ b/arch/x86/xen/Kconfig > > @@ -50,3 +50,13 @@ config XEN_DEBUG_FS > > Enable statistics output and various tuning options in > > debugfs. Enabling this option may incur a significant performance > > overhead. > > +config XEN_X86_PVH > > + bool "Support for running as a PVH guest (EXPERIMENTAL)" > > + depends on X86_64 && XEN && INTEL_IOMMU && EXPERIMENTAL > > OOI why does the kernel side require an INTEL_IOMMU? I can see why the > hypervisor would need it but the guests (including dom0) can't > actually see the underlying IOMMU, can they? Well, the kernel requires the hypervisor to have it, but I guess thats not what this is referring to. The tools can decide that. I'll take it out. -- 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/
Powered by blists - more mailing lists