[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54F8D3D8.3060406@zytor.com>
Date: Thu, 05 Mar 2015 14:08:24 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
CC: David Vrabel <david.vrabel@...rix.com>,
Sarah Newman <srn@...mr.com>, linux-kernel@...r.kernel.org,
xen-devel@...ts.xen.org, Ingo Molnar <mingo@...hat.com>,
Suresh Siddha <sbsiddha@...il.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [Xen-devel] [PATCHv1] x86: don't schedule when handling #NM exception
On 06/23/2014 06:08 AM, Konrad Rzeszutek Wilk wrote:
> On Wed, Mar 19, 2014 at 08:02:22AM -0700, H. Peter Anvin wrote:
>> On 03/19/2014 06:21 AM, Konrad Rzeszutek Wilk wrote:
>>>>
>>>> The following patch does the always eager allocation. It's a fixup of
>>>> Suresh's original patch.
>>>>
>>>
>>> Hey Peter,
>>>
>>> I think this is the solution you were looking for?
>>>
>>> Or are there some other subtle issues that you think lurk around?
>>>
>>
>> Ah, I managed to miss it (mostly because it was buried *inside* another
>> email and didn't change the subject line... I really dislike that mode
>> of delivering a patch.
>
> Let me roll up some of these patchset and send them as git send-email.
>
>>
>> Let me see if the issues have been fixed. Still wondering if there is a
>> way we can get away without the boot_func hack...
>
> I have to confesss I don't even remember what the 'if the issues have been
> fixed' is referring to?
>
Hi Konrad... it looks like this got left waiting for you and got forgotten?
-hpa
--
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