From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Carsten Otte <cotte@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Sebastian Ott <sebott@linux.vnet.ibm.com>
Subject: Re: [PATCH v2 7/7] s390/kvm: In-kernel channel subsystem support.
Date: Wed, 19 Sep 2012 17:57:26 +0300 [thread overview]
Message-ID: <5059DD56.2000909@redhat.com> (raw)
In-Reply-To: <48430489-B96F-4717-AA1E-B04445F55717@suse.de>
On 09/19/2012 05:47 PM, Alexander Graf wrote:
>
> On 04.09.2012, at 17:13, Cornelia Huck wrote:
>
>> Handle most support for channel I/O instructions in the kernel itself.
>>
>> Only asynchronous functions (such as the start function) need to be
>> handled by userspace.
>
> Phew. This is a lot of code for something that is usually handled in user space in the kvm world. The x86 equivalent would be an in-kernel PCI bus, right? Have you measured major performance penalties when running this from user space?
>
> Avi, what do you think?
I know nothing of this stuff. But your request for numbers is justified
of course.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: linux-s390 <linux-s390@vger.kernel.org>,
Anthony Liguori <aliguori@us.ibm.com>,
Rusty Russell <rusty@rustcorp.com.au>, KVM <kvm@vger.kernel.org>,
Carsten Otte <cotte@de.ibm.com>,
Sebastian Ott <sebott@linux.vnet.ibm.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2 7/7] s390/kvm: In-kernel channel subsystem support.
Date: Wed, 19 Sep 2012 17:57:26 +0300 [thread overview]
Message-ID: <5059DD56.2000909@redhat.com> (raw)
In-Reply-To: <48430489-B96F-4717-AA1E-B04445F55717@suse.de>
On 09/19/2012 05:47 PM, Alexander Graf wrote:
>
> On 04.09.2012, at 17:13, Cornelia Huck wrote:
>
>> Handle most support for channel I/O instructions in the kernel itself.
>>
>> Only asynchronous functions (such as the start function) need to be
>> handled by userspace.
>
> Phew. This is a lot of code for something that is usually handled in user space in the kvm world. The x86 equivalent would be an in-kernel PCI bus, right? Have you measured major performance penalties when running this from user space?
>
> Avi, what do you think?
I know nothing of this stuff. But your request for numbers is justified
of course.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-09-19 14:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 15:13 [RFC PATCH v2 0/7] s390: virtual css host support Cornelia Huck
2012-09-04 15:13 ` [Qemu-devel] " Cornelia Huck
2012-09-04 15:13 ` [PATCH v2 1/7] s390/kvm: Support for I/O interrupts Cornelia Huck
2012-09-04 15:13 ` [Qemu-devel] " Cornelia Huck
2012-09-05 7:28 ` Avi Kivity
2012-09-05 7:28 ` [Qemu-devel] " Avi Kivity
2012-09-05 8:26 ` Cornelia Huck
2012-09-05 8:26 ` [Qemu-devel] " Cornelia Huck
2012-09-04 15:13 ` [PATCH v2 2/7] s390/kvm: Add support for machine checks Cornelia Huck
2012-09-04 15:13 ` [Qemu-devel] " Cornelia Huck
2012-09-05 7:22 ` Heiko Carstens
2012-09-05 7:22 ` [Qemu-devel] " Heiko Carstens
2012-09-05 8:39 ` Cornelia Huck
2012-09-05 8:39 ` [Qemu-devel] " Cornelia Huck
2012-09-04 15:13 ` [PATCH v2 3/7] s390/kvm: In-kernel handling of I/O instructions Cornelia Huck
2012-09-04 15:13 ` [Qemu-devel] " Cornelia Huck
2012-09-04 15:13 ` [PATCH v2 4/7] s390: Move css limits from drivers/s390/cio/ to include/asm/ Cornelia Huck
2012-09-04 15:13 ` [Qemu-devel] " Cornelia Huck
2012-09-04 15:13 ` [PATCH v2 5/7] s390: Make some css-related structures usable by non-cio code Cornelia Huck
2012-09-04 15:13 ` [Qemu-devel] " Cornelia Huck
2012-09-04 15:13 ` [PATCH v2 6/7] s390/kvm: Base infrastructure for enabling capabilities Cornelia Huck
2012-09-04 15:13 ` [Qemu-devel] " Cornelia Huck
2012-09-04 15:13 ` [PATCH v2 7/7] s390/kvm: In-kernel channel subsystem support Cornelia Huck
2012-09-04 15:13 ` [Qemu-devel] " Cornelia Huck
2012-09-19 14:47 ` Alexander Graf
2012-09-19 14:47 ` [Qemu-devel] " Alexander Graf
2012-09-19 14:57 ` Avi Kivity [this message]
2012-09-19 14:57 ` Avi Kivity
2012-09-20 7:26 ` Christian Borntraeger
2012-09-20 7:26 ` [Qemu-devel] " Christian Borntraeger
2012-09-05 7:51 ` [RFC PATCH v2 0/7] s390: virtual css host support Avi Kivity
2012-09-05 7:51 ` [Qemu-devel] " Avi Kivity
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=5059DD56.2000909@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
--cc=schwidefsky@de.ibm.com \
--cc=sebott@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.