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: <alpine.LFD.2.00.1102081544290.31804@localhost6.localdomain6> Date: Tue, 8 Feb 2011 15:55:00 +0100 (CET) From: Thomas Gleixner <tglx@...utronix.de> To: Ian Campbell <Ian.Campbell@...rix.com> cc: Jeremy Fitzhardinge <jeremy@...p.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [patch 0/4] XEN: Interrupt cleanups On Tue, 8 Feb 2011, Ian Campbell wrote: > On Mon, 2011-02-07 at 13:57 -0800, Jeremy Fitzhardinge wrote: > > On 02/07/2011 01:33 PM, Thomas Gleixner wrote: > > > Ok. The irq_chip conversion is mostly mechanical, but I'm really > > > concerned about that IRQ_SUSPENDED hackery. It'd be nice if you > > > resp. Ian could give that a test ride. That would allow me to cleanup > > > stuff in the core code. > > > > Ian notes: "tglx's 4 patch interrupt cleanup series on LKML causes some > > oddities on PV migration. Will dig further tomorrow..." > > > > So it looks like there's still something amiss. > > The patches missed an indirect use of IRQF_NO_SUSPEND pulled in via > IRQF_TIMER. The following fixed things for me (probably belongs in your > patch 4/4). > > With this fixlet PV guest migration works just fine. I also booted the > entire series as a dom0 kernel and it appeared fine. > > I also tested alongside the cleanup patches Jeremy mentioned before and > as expected there is no interaction. > > So, with the fixes to 2/4 (irq_move_irq think from yesterday) and 4/4 > (below), the entire series is: > Acked-by: Ian Campbell <ian.campbell@...rix.com> Cool. So what's the best way to proceed ? That code is not yet in linus tree, right ? So I guess the best way is that I add the core changes to a rc-4 based branch and you can pull it in and apply the whole xen stuff to your own tree. I base my pending patches on top of that so it wont be any problem when merging the stuff together in next or linus later. Thanks, tglx -- 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