From: "H. Peter Anvin" <hpa@zytor.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Josh Boyer <jwboyer@redhat.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
mingo@redhat.com, tglx@linutronix.de, rostedt@goodmis.org,
kraman@redhat.com, gregkh@linuxfoundation.org,
stable@vger.kernel.org, bp@alien8.de,
samu.kallio@aberdeencloud.com, xen-devel@lists.xen.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/x86: Patch out arch_flush_lazy_mmu_mode() when running on bare metal
Date: Fri, 22 Mar 2013 13:25:21 -0700 [thread overview]
Message-ID: <9a798a0e-bc39-40db-be7f-b5e6fcc382d9@email.android.com> (raw)
In-Reply-To: <20130322200941.GB6189@phenom.dumpdata.com>
Sure.
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
>On Wed, Mar 20, 2013 at 08:08:45PM -0400, Josh Boyer wrote:
>> On Wed, Mar 20, 2013 at 06:53:55AM -0700, Boris Ostrovsky wrote:
>> >
>> > ----- jwboyer@redhat.com wrote:
>> >
>> > > On Wed, Mar 13, 2013 at 09:25:44AM -0400, Boris Ostrovsky wrote:
>> > > > On 03/01/2013 07:14 AM, Josh Boyer wrote:
>> > > > >On Thu, Feb 28, 2013 at 04:52:20PM -0800, H. Peter Anvin
>wrote:
>> > > > >>On 02/28/2013 04:42 PM, Josh Boyer wrote:
>> > > > >>>On Fri, Mar 01, 2013 at 01:36:29AM +0100, Borislav Petkov
>wrote:
>> > > > >>>>On Thu, Feb 28, 2013 at 04:15:45PM -0800, H. Peter Anvin
>wrote:
>> > > > >>>>>>I'll try to get someone to test this tomorrow.
>> > > > >>>>Btw, you'd need to apply that other patch too
>> > > > >>>>
>> > > > >>>>http://marc.info/?l=xen-devel&m=136206183814547&w=2
>> > > > >>>>
>> > > > >>>>so that arch_flush_lazy_mmu_mode() has at least one caller
>on
>> > > x86_64.
>> > > > >>>Yeah, we already have that applied. It stops crashes in xen
>> > > > >>>environments so we pulled it in as a bugfix. Thanks though!
>> > > > >>>
>> > > > >>Who are "we"?
>> > > > >Sorry, Fedora. That patch has a link to a bug in it. We
>applied
>> > > the
>> > > > >patch for that bug. I'll apply Boris' patch on top and get
>the
>> > > same
>> > > > >people to test it.
>> > > >
>> > > > Josh, have you had a chance to test this?
>> > >
>> > > I've tested it on bare metal for a while now. No problems
>noticed at
>> > > all. I've not heard back from Krishna who was testing it in the
>Xen
>> > > environment. Krishna?
>> >
>> >
>> > Any updates?
>>
>> No. I've still not heard from Krishna.
>>
>> At this point I've tested it on bare metal quite a bit, and Konrad
>has
>> tested it on both bare metal and Xen. That should already cover the
>> case Krishna was going to test anyway. I suggest we move forward and
>> take the patch.
>
>Peter?
>
>Would you like me or Boris to clean up the two patches with the
>appropiate Acks and send them to you?
>>
>> josh
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
next prev parent reply other threads:[~2013-03-22 20:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 13:53 Boris Ostrovsky
2013-03-21 0:08 ` Josh Boyer
2013-03-22 20:09 ` Konrad Rzeszutek Wilk
2013-03-22 20:25 ` H. Peter Anvin [this message]
2013-03-23 13:36 ` [PATCH 1/2] x86: mm: Fix vmalloc_fault oops during lazy MMU updates Konrad Rzeszutek Wilk
2013-03-23 13:36 ` [PATCH 2/2] mm/x86: Patch out arch_flush_lazy_mmu_mode() when running on bare metal Konrad Rzeszutek Wilk
2013-04-03 13:26 ` Boris Ostrovsky
2013-04-11 0:30 ` [tip:x86/urgent] x86, mm: " tip-bot for Boris Ostrovsky
2013-04-11 15:17 ` Boris Ostrovsky
2013-04-11 0:29 ` [tip:x86/urgent] x86, mm, paravirt: Fix vmalloc_fault oops during lazy MMU updates tip-bot for Samu Kallio
-- strict thread matches above, loose matches on Subject: below --
2013-02-28 22:55 [PATCH] mm/x86: Patch out arch_flush_lazy_mmu_mode() when running on bare metal Boris Ostrovsky
2013-02-28 23:37 ` Borislav Petkov
2013-03-01 0:05 ` Josh Boyer
2013-03-01 0:15 ` H. Peter Anvin
2013-03-01 0:36 ` Borislav Petkov
2013-03-01 0:42 ` Josh Boyer
2013-03-01 0:52 ` H. Peter Anvin
2013-03-01 12:14 ` Josh Boyer
2013-03-13 13:25 ` Boris Ostrovsky
2013-03-13 13:44 ` Josh Boyer
2013-03-21 14:07 ` Konrad Rzeszutek Wilk
2013-03-04 15:13 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9a798a0e-bc39-40db-be7f-b5e6fcc382d9@email.android.com \
--to=hpa@zytor.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=jwboyer@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=kraman@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=samu.kallio@aberdeencloud.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome