From: Paolo Bonzini <pbonzini@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "He Chen" <he.chen@linux.intel.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>,
"Luwei Kang" <luwei.kang@intel.com>,
"Piotr Luc" <Piotr.Luc@intel.com>
Subject: Re: [PATCH v3] x86/cpuid: expose AVX512_4VNNIW and AVX512_4FMAPS features to kvm guest
Date: Fri, 4 Nov 2016 16:58:50 +0100 [thread overview]
Message-ID: <19ce3689-8a73-9692-e48b-95a2cbdc8dc9@redhat.com> (raw)
In-Reply-To: <20161104155752.e6gf7hev3tklbw6m@pd.tnic>
On 04/11/2016 16:57, Borislav Petkov wrote:
> On Fri, Nov 04, 2016 at 04:13:24PM +0100, Paolo Bonzini wrote:
>> I mean that the changes to scattered.c are small, so it makes no sense
>> to split them. With an Acked-by I could simply take the patch into my
>> tree.
>
> On no, it is not about the size or which tree it goes thru - rather that
> having stuff separated conceptually makes the patches much more clear.
>
> The patch order would be
>
> * modify scattered.c to return leaf
> * add user of new function
>
> which also makes review almost trivial.
That's fine by me of course. I would probably take both patches anyway.
Paolo
next prev parent reply other threads:[~2016-11-04 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 7:07 [PATCH v3] x86/cpuid: expose AVX512_4VNNIW and AVX512_4FMAPS features to kvm guest He Chen
2016-11-04 10:52 ` Borislav Petkov
2016-11-04 14:53 ` Paolo Bonzini
2016-11-04 15:06 ` Borislav Petkov
2016-11-04 15:13 ` Paolo Bonzini
2016-11-04 15:57 ` Borislav Petkov
2016-11-04 15:58 ` Paolo Bonzini [this message]
2016-11-07 16:52 ` Thomas Gleixner
2016-11-07 2:10 ` He Chen
2016-11-07 9:05 ` Borislav Petkov
2016-11-07 16:47 ` Thomas Gleixner
2016-11-07 17:07 ` Borislav Petkov
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=19ce3689-8a73-9692-e48b-95a2cbdc8dc9@redhat.com \
--to=pbonzini@redhat.com \
--cc=Piotr.Luc@intel.com \
--cc=bp@alien8.de \
--cc=he.chen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luwei.kang@intel.com \
--cc=mingo@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).