All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	KVM <kvm@vger.kernel.org>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Alexander Graf <agraf@suse.de>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	Jens Freimann <jfrei@linux.vnet.ibm.com>,
	Ekaterina Tumanova <tumanova@linux.vnet.ibm.com>
Subject: Re: [PATCH/RFC 5/9] KVM: s390: introduce post handlers for STSI
Date: Mon, 16 Mar 2015 13:22:53 +0100	[thread overview]
Message-ID: <5506CB1D.7030509@redhat.com> (raw)
In-Reply-To: <5506CA1B.5000605@de.ibm.com>



On 16/03/2015 13:18, Christian Borntraeger wrote:
> Its up to a page and the content depends on the function code, selector1
> and selector2.
> See arch/s390/kernel/sysinfo.c for the details or zarchitecture principles of
> opration the STSI instruction.
> 
> 
> Some time ago we had patches that passed the guest name
> and UUID into the kernel - then Alex Graf asked, why we cant do that in 
> userspace.
> https://lists.nongnu.org/archive/html/qemu-devel/2014-04/msg00094.html
> 
> Now, stsi also gives the bare information as provides by upper
> layers: e.g. 2.2.2 gives basic LPAR information. When doing that under
> KVM or z/VM, KVM or z/VM will pass that information along to the underlying 
> LPAR hypervisor and give the result back to the guest.
> 
> So I came up with the idea to let KVM do what it needs but also allow
> QEMU to override (3.2.2 - this 2nd level hypervisor)

If it's up to a page it definitely makes sense to do it this way.

Thanks,

Paolo

  reply	other threads:[~2015-03-16 12:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16  8:51 [PATCH/RFC 0/9] Next bunch of KVM/s390x changes for next Christian Borntraeger
2015-03-16  8:51 ` [PATCH/RFC 1/9] KVM: s390: Spelling s/intance/instance/ Christian Borntraeger
2015-03-16  8:51 ` [PATCH/RFC 2/9] KVM: s390: cleanup jump lables in kvm_arch_init_vm Christian Borntraeger
2015-03-16 12:43   ` Cornelia Huck
2015-03-16  8:51 ` [PATCH/RFC 3/9] KVM: s390: Fix low-address protection for real addresses Christian Borntraeger
2015-03-16 12:48   ` Cornelia Huck
2015-03-16  8:51 ` [PATCH/RFC 4/9] KVM: s390: Add MEMOP ioctls for reading/writing guest memory Christian Borntraeger
2015-03-16 12:16   ` Cornelia Huck
2015-03-16 12:23     ` Christian Borntraeger
2015-03-19  0:23   ` Marcelo Tosatti
2015-03-16  8:51 ` [PATCH/RFC 5/9] KVM: s390: introduce post handlers for STSI Christian Borntraeger
2015-03-16 11:55   ` Paolo Bonzini
2015-03-16 12:18     ` Christian Borntraeger
2015-03-16 12:22       ` Paolo Bonzini [this message]
2015-03-16  8:51 ` [PATCH/RFC 6/9] KVM: s390: Guest's memory access functions get access registers Christian Borntraeger
2015-03-16 13:12   ` Cornelia Huck
2015-03-16  8:51 ` [PATCH/RFC 7/9] KVM: s390: Optimize paths where get_vcpu_asce() is invoked Christian Borntraeger
2015-03-16 13:13   ` Cornelia Huck
2015-03-16  8:51 ` [PATCH/RFC 8/9] KVM: s390: Add access register mode Christian Borntraeger
2015-03-16  8:51 ` [PATCH/RFC 9/9] KVM: s390: Create ioctl for Getting/Setting guest storage keys Christian Borntraeger
2015-03-16 13:07   ` 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=5506CB1D.7030509@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=jfrei@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=tumanova@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.