qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	qemu-s390x <qemu-s390x@nongnu.org>,
	Alexander Graf <agraf@suse.de>, Thomas Huth <thuth@redhat.com>,
	David Hildenbrand <david@redhat.com>,
	Richard Henderson <rth@twiddle.net>,
	Janosch Frank <frankja@linux.vnet.ibm.com>,
	Halil Pasic <pasic@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/3] s390x/kvm: implement new hardware/firmware features
Date: Thu, 18 Jan 2018 12:53:22 +0100	[thread overview]
Message-ID: <20180118125322.252929dc.cohuck@redhat.com> (raw)
In-Reply-To: <20180118085628.40798-1-borntraeger@de.ibm.com>

On Thu, 18 Jan 2018 09:56:25 +0100
Christian Borntraeger <borntraeger@de.ibm.com> wrote:

> We want to provide more hw features to guests, namely the new bpb
> control as well as other transparent facilities that might be
> introduced by firmware updates (e.g. the stfle facility 81).
> 
> See the kernel discussion for the KVM side
> https://www.spinics.net/lists/kernel/msg2700551.html
> 
> v2->v3: - use bool for bpbc
> 	- sort cpu facilities
> v1->v2: - style and comment fixes
> 	- drop transparent facility patch
> 	- add patch to introduce facility 81
> 
> Christian Borntraeger (3):
>   header sync
>   s390x/kvm: Handle bpb feature
>   s390x/kvm: provide stfle.81
> 
>  linux-headers/asm-s390/kvm.h    |  9 ++++-----
>  linux-headers/linux/kvm.h       |  5 +++--
>  target/s390x/cpu.c              |  1 +
>  target/s390x/cpu.h              |  1 +
>  target/s390x/cpu_features.c     |  2 ++
>  target/s390x/cpu_features_def.h |  2 ++
>  target/s390x/gen-features.c     |  2 ++
>  target/s390x/kvm.c              | 14 ++++++++++++++
>  target/s390x/machine.c          | 17 +++++++++++++++++
>  9 files changed, 46 insertions(+), 7 deletions(-)
> 

Thanks, I've queued this. Once the bpb code lands in Linux, I'll
replace patch 1 with a proper header sync and push to s390-next.

  parent reply	other threads:[~2018-01-18 11:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18  8:56 [Qemu-devel] [PATCH v3 0/3] s390x/kvm: implement new hardware/firmware features Christian Borntraeger
2018-01-18  8:56 ` [Qemu-devel] [PATCH v3 1/3] header sync Christian Borntraeger
2018-01-18 11:42   ` David Hildenbrand
2018-01-22  8:31     ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-01-22  8:47       ` Cornelia Huck
2018-01-18  8:56 ` [Qemu-devel] [PATCH v3 2/3] s390x/kvm: Handle bpb feature Christian Borntraeger
2018-01-18 11:42   ` Thomas Huth
2018-01-18 11:43   ` David Hildenbrand
2018-01-18 12:01   ` Halil Pasic
2018-01-18 12:09     ` Christian Borntraeger
2018-01-18  8:56 ` [Qemu-devel] [PATCH v3 3/3] s390x/kvm: provide stfle.81 Christian Borntraeger
2018-01-18 11:05   ` Halil Pasic
2018-01-18 11:43   ` David Hildenbrand
2018-01-18 11:43   ` Thomas Huth
2018-01-18 11:53 ` Cornelia Huck [this message]
2018-01-18 12:47   ` [Qemu-devel] [PATCH v3 0/3] s390x/kvm: implement new hardware/firmware features Christian Borntraeger
2018-01-18 13:15     ` Cornelia Huck
2018-01-18 13:31       ` Christian Ehrhardt
2018-01-18 14:48         ` Cornelia Huck
2018-01-22 10:20 ` Cornelia Huck

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=20180118125322.252929dc.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.vnet.ibm.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=thuth@redhat.com \
    /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).