| 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 PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 28 Oct 2009 10:06:55 -0600 From: Alex Williamson <alex.williamson@...com> To: David Woodhouse <dwmw2@...radead.org> Cc: iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org Subject: Re: [PATCH 4/5] intel-iommu: Reinstate RMRRs if a device is removed from passthrough domain On Wed, 2009-10-28 at 14:36 +0000, David Woodhouse wrote: > On Tue, 2009-10-27 at 09:50 -0600, Alex Williamson wrote: > > > > Yes, good point. I'm not seeing any convenient ways to setup a new > > domain for a device while it's still a member of the si_domain. It > > looks like I'd need to extract parts of the get_valid_domain_for_dev() > > path and ignore any bits about using the already existing domain. > > That seems like a sane plan. That code wants cleaning up anyway, and > factoring out the 'make new domain' part of get_valid_domain_for_dev() > should be simple enough. Ok, I'll work on something along those lines. FWIW, even though I sent these as a series, each one stands on it's own. While I think reinstating RMRRs is the right thing to do, I don't know of any devices that break with the current model (the device I know of with the interesting RMRR usage shouldn't be demoted from the si_domain). So please consider pushing patches 2, 3 & 5 upstream (particularly 2). Thanks, Alex -- 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