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
| ||
|
Date: Tue, 28 Nov 2017 02:46:53 -0700 From: "Jan Beulich" <JBeulich@...e.com> To: "Christian König" <christian.koenig@....com> Cc: <helgaas@...nel.org>, <amd-gfx@...ts.freedesktop.org>, <dri-devel@...ts.freedesktop.org>, "xen-devel" <xen-devel@...ts.xen.org>, "Boris Ostrovsky" <boris.ostrovsky@...cle.com>, <linux-kernel@...r.kernel.org>, <linux-pci@...r.kernel.org> Subject: Re: [Xen-devel] [PATCH v9 4/5] x86/PCI: Enable a 64bit BAR on AMD Family 15h (Models 30h-3fh) Processors v5 >>> On 28.11.17 at 10:12, <christian.koenig@....com> wrote: > In theory the BIOS would search for address space and won't find > anything, so the hotplug operation should fail even before it reaches > the kernel in the first place. How would the BIOS know what the OS does or plans to do? I think it's the other way around - the OS needs to avoid using any regions for MMIO which are marked as hotpluggable in SRAT. Since there is no vNUMA yet for Xen Dom0, that would need special handling. Jan
Powered by blists - more mailing lists