| 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: Mon, 18 May 2009 10:36:09 +0900 From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> To: jeremy@...p.org Cc: mingo@...e.hu, x86@...nel.org, linux-kernel@...r.kernel.org, xen-devel@...ts.xensource.com, gregkh@...e.de, okir@...e.de Subject: Re: Where do we stand with the Xen patches? On Thu, 14 May 2009 12:54:54 -0700 Jeremy Fitzhardinge <jeremy@...p.org> wrote: > Hi Ingo, > > Over the last week or so, I've set out pull requests for the following > branches in git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git : > > for-ingo/xen/dom0/core > > You made two comments about the first post of this set: > > 1. The // comments in the mtrr code. Now fixed. > 2. A query about when Xen can support PAT. In progress; when its > done, we can remove the unconditional PAT disable. > > for-ingo/xen/dom0/pci > for-ingo/xen/dom0/swiotlb > > Updated with Joerg Roedel, FUJITA Tomonori and Matthew Wilcox's > comments, Acked-by and Reviewed-bys as appropriate. The original code added dom0-specific dma mapping stuff in the generic place, which is completely wrong. I asked you to move the hacky stuff to Xen-specific code and ack'ed the patchset. But as I said again and again, the dom0 changes to the generic dma mapipng code is really ugly and I don't like them at all. I didn't ack'ed such changes. -- 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