From: Ingo Molnar <mingo@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jan Beulich <JBeulich@suse.com>,
mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3, v2] x86: xor-block handling adjustments
Date: Sat, 26 Jan 2013 13:08:53 +0100 [thread overview]
Message-ID: <20130126120853.GE13445@gmail.com> (raw)
In-Reply-To: <5102DD08.9080204@zytor.com>
* H. Peter Anvin <hpa@zytor.com> wrote:
> On 01/25/2013 12:21 AM, Jan Beulich wrote:
> >>
> >> I don't see anything wrong, except that I can't *find* patch 3/3 either
> >> in my inbox nor on LKML...
> >
> > I can certainly resend the whole set, but our email system even
> > got a delivery confirmation from yours on patch 3 (other than
> > e.g. from Ingo's, and all of this identical to 0...2).
> >
> > Or see https://patchwork.kernel.org/patch/1688991/, according
> > to which you even responded to it (which is the concern Ingo was
> > referring to).
> >
>
> Ah yes, now I have the context.
>
> And with that, I have to NAK the patch. I did talk to the KVM
> people and they confirmed that this is NOT something they
> want. They do not program VT-x to VMEXIT on CR0 changes.
>
> So this is Xen-specific, and penalizing other hypervisors is
> wrong.
Are patches #1 and #2 still OK?
Thanks,
Ingo
next prev parent reply other threads:[~2013-01-26 12:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 14:17 [PATCH 0/3, v2] x86: xor-block handling adjustments Jan Beulich
2013-01-24 17:15 ` Ingo Molnar
2013-01-24 17:32 ` H. Peter Anvin
2013-01-25 8:21 ` Jan Beulich
2013-01-25 8:25 ` Ingo Molnar
2013-01-25 19:29 ` H. Peter Anvin
2013-01-26 12:08 ` Ingo Molnar [this message]
2013-01-26 15:13 ` H. Peter Anvin
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=20130126120853.GE13445@gmail.com \
--to=mingo@kernel.org \
--cc=JBeulich@suse.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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