linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Morel <pmorel@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
	borntraeger@de.ibm.com, frankja@linux.ibm.com, cohuck@redhat.com,
	david@redhat.com, thuth@redhat.com, imbrenda@linux.ibm.com,
	hca@linux.ibm.com, gor@linux.ibm.com, pmorel@linux.ibm.com
Subject: [PATCH v2 0/2] s390x: KVM: CPU Topology
Date: Thu, 22 Jul 2021 19:02:31 +0200	[thread overview]
Message-ID: <1626973353-17446-1-git-send-email-pmorel@linux.ibm.com> (raw)

To provide Topology information to the guest through the STSI
instruction, we need to forward STSI with Function Code 15 to
QEMU which will take care to provide the right information to
the guest.

To let the guest use the PTF instruction and ask if a topology
change occured we add a new KVM capability to enable the topology
facility.


Pierre Morel (2):
  s390x: KVM: accept STSI for CPU topology information
  s390:kvm: Topology expose TOPOLOGY facility

 arch/s390/kvm/kvm-s390.c | 1 +
 arch/s390/kvm/priv.c     | 7 ++++++-
 include/uapi/linux/kvm.h | 1 +
 3 files changed, 8 insertions(+), 1 deletion(-)

-- 
2.25.1

Changelog:

- Add a KVM capability to let QEMU know we support PTF and STSI 15
  (David)

- check KVM facility 11 before accepting STSI fc 15
  (David)

- handle all we can in userland
  (David)

- add tracing to STSI fc 15
  (Connie)


             reply	other threads:[~2021-07-22 17:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22 17:02 Pierre Morel [this message]
2021-07-22 17:02 ` [PATCH v2 1/2] s390x: KVM: accept STSI for CPU topology information Pierre Morel
2021-07-23  8:34   ` Christian Borntraeger
2021-07-22 17:02 ` [PATCH v2 2/2] s390:kvm: Topology expose TOPOLOGY facility Pierre Morel
2021-07-23  8:14   ` Christian Borntraeger
2021-07-23  8:55     ` Cornelia Huck
2021-07-23  9:28       ` Christian Borntraeger
2021-07-23 10:10         ` Pierre Morel
2021-07-23 10:24           ` Christian Borntraeger

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=1626973353-17446-1-git-send-email-pmorel@linux.ibm.com \
    --to=pmorel@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --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).