[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56CB17ED.7030804@oracle.com>
Date: Mon, 22 Feb 2016 09:15:09 -0500
From: Boris Ostrovsky <boris.ostrovsky@...cle.com>
To: "Luis R. Rodriguez" <mcgrof@...e.com>
Cc: "Luis R. Rodriguez" <mcgrof@...nel.org>, bp@...en8.de,
x86@...nel.org, linux-kernel@...r.kernel.org, luto@...capital.net,
rusty@...tcorp.com.au, david.vrabel@...rix.com,
konrad.wilk@...cle.com, xen-devel@...ts.xensource.com
Subject: Re: [PATCH 5/9] apm32: remove paravirt_enabled() use
On 02/19/2016 07:42 PM, Luis R. Rodriguez wrote:
> On Fri, Feb 19, 2016 at 05:17:27PM -0500, Boris Ostrovsky wrote:
>>
>> On 02/19/2016 03:58 PM, Luis R. Rodriguez wrote:
>>> On Fri, Feb 19, 2016 at 10:08:43AM -0500, Boris Ostrovsky wrote:
>>>
>>>> in xen_start_kernel(). Better yet, clear whole .bss.
>>>>
>>>> (This applies to the next patch as well).
>>> So clear_bss() -- oh look, another call that xen_start_kernel() could have made
>>> good use of. :) Can you send a respective patch I can old into this series?
>>> I'm afraid it is by no means obvious to me where it would be safe to do this on
>>> xen_start_kernel().
>> OK, I'll test it next week, it really should be done irrespective of
>> what you are doing here.
> OK so it can go in separately?
Yes, I'll send it as a separate patch.
-boris
Powered by blists - more mailing lists