From: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
To: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
qemu-devel@nongnu.org, renxiaof@linux.vnet.ibm.com,
cornelia.huck@de.ibm.com, borntraeger@de.ibm.com, agraf@suse.com,
alex.williamson@redhat.com, pmorel@linux.vnet.ibm.com,
pasic@linux.vnet.ibm.com, wkywang@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH RFC v2 03/12] s390x/css: add s390-map-css machine option
Date: Fri, 17 Feb 2017 10:08:15 +0800 [thread overview]
Message-ID: <20170217020815.GA28001@bjsdjshi@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170112072513.98411-4-bjsdjshi@linux.vnet.ibm.com>
* Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com> [2017-01-12 08:25:04 +0100]:
> From: Xiao Feng Ren <renxiaof@linux.vnet.ibm.com>
>
> We want to support real (i.e. not virtual) channel devices
> even for guests that do not support MCSS-E (where guests may
> see devices from any channel subsystem image at once). As all
> virtio-ccw devices are in css 0xfe (and show up in the default
> css 0 for guests not activating MCSS-E), we need an option to
> map e.g. passed-through subchannels from their real css (0-3,
> or 0 for hosts not activating MCSS-E) into the default css.
> This will be exploited in a later patch.
After some brainstorming, we decided to change this interface a bit.
The first thing is that, we agreed that "s390-squash-mcss" is a better
name than "s390-map-css". The new name denotes that it is trying to
accommodate the devices from multiple channel subsystems into a
non-mcsse-e system, and the word "suqash" is more accurate about what
is happening internally.
The second thing is, we should never map/squash a vfio-ccw device into
css 0xfe, which is reserved for virtio device only. So when squashing,
we need to do it the other way around (i.e. have virtio devices at
0.x.xxxx instead of fe.x.xxxx to accommodate non-mcsse-e).
>
> Signed-off-by: Xiao Feng Ren <renxiaof@linux.vnet.ibm.com>
[...]
--
Dong Jia
next prev parent reply other threads:[~2017-02-17 2:08 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 7:25 [PATCH RFC v2 00/12] basic channel IO passthrough infrastructure based on vfio Dong Jia Shi
2017-01-12 7:25 ` [Qemu-devel] " Dong Jia Shi
2017-01-12 7:25 ` [PATCH RFC v2 01/12] update-linux-headers: add asm-s390/vfio_ccw.h Dong Jia Shi
2017-01-12 7:25 ` [Qemu-devel] " Dong Jia Shi
2017-01-12 7:25 ` [PATCH RFC v2 02/12] vfio: linux-headers update for vfio-ccw Dong Jia Shi
2017-01-12 7:25 ` [Qemu-devel] " Dong Jia Shi
2017-01-17 21:51 ` Alex Williamson
2017-01-17 21:51 ` [Qemu-devel] " Alex Williamson
2017-01-18 2:51 ` Dong Jia Shi
2017-01-18 12:41 ` Cornelia Huck
2017-01-18 12:41 ` [Qemu-devel] " Cornelia Huck
2017-01-18 20:43 ` Alex Williamson
2017-01-18 20:43 ` [Qemu-devel] " Alex Williamson
2017-01-19 1:54 ` Dong Jia Shi
2017-01-19 1:54 ` Dong Jia Shi
2017-01-18 2:51 ` Dong Jia Shi
2017-01-12 7:25 ` [PATCH RFC v2 03/12] s390x/css: add s390-map-css machine option Dong Jia Shi
2017-01-12 7:25 ` [Qemu-devel] " Dong Jia Shi
2017-02-17 2:08 ` Dong Jia Shi
2017-02-17 2:08 ` Dong Jia Shi [this message]
2017-01-12 7:25 ` [PATCH RFC v2 04/12] s390x/css: realize css_sch_build_schib Dong Jia Shi
2017-01-12 7:25 ` [Qemu-devel] " Dong Jia Shi
2017-01-12 7:25 ` [PATCH RFC v2 05/12] s390x/css: realize css_create_sch Dong Jia Shi
2017-01-12 7:25 ` [Qemu-devel] " Dong Jia Shi
2017-01-12 7:25 ` [PATCH RFC v2 06/12] s390x/css: device support for s390-ccw passthrough Dong Jia Shi
2017-01-12 7:25 ` [Qemu-devel] " Dong Jia Shi
2017-01-12 7:25 ` [PATCH RFC v2 07/12] vfio/ccw: vfio based subchannel passthrough driver Dong Jia Shi
2017-01-12 7:25 ` [Qemu-devel] " Dong Jia Shi
2017-01-17 22:49 ` Alex Williamson
2017-01-17 22:49 ` [Qemu-devel] " Alex Williamson
2017-01-18 3:22 ` Dong Jia Shi
2017-01-18 3:22 ` Dong Jia Shi
2017-01-12 7:25 ` [PATCH RFC v2 08/12] vfio/ccw: get io region info Dong Jia Shi
2017-01-12 7:25 ` [Qemu-devel] " Dong Jia Shi
2017-01-17 22:49 ` Alex Williamson
2017-01-17 22:49 ` [Qemu-devel] " Alex Williamson
2017-01-18 5:22 ` Dong Jia Shi
2017-01-18 5:22 ` [Qemu-devel] " Dong Jia Shi
2017-01-18 5:51 ` Dong Jia Shi
2017-01-18 5:51 ` Dong Jia Shi
2017-01-12 7:25 ` [PATCH RFC v2 09/12] vfio/ccw: get irqs info and set the eventfd fd Dong Jia Shi
2017-01-12 7:25 ` [Qemu-devel] " Dong Jia Shi
2017-01-17 22:53 ` Alex Williamson
2017-01-17 22:53 ` [Qemu-devel] " Alex Williamson
2017-01-18 5:55 ` Dong Jia Shi
2017-01-18 5:55 ` Dong Jia Shi
2017-01-12 7:25 ` [PATCH RFC v2 10/12] s390x/css: introduce and realize ccw-request callback Dong Jia Shi
2017-01-12 7:25 ` [Qemu-devel] " Dong Jia Shi
2017-01-12 7:25 ` [PATCH RFC v2 11/12] s390x/css: ccws translation infrastructure Dong Jia Shi
2017-01-12 7:25 ` [Qemu-devel] " Dong Jia Shi
2017-01-12 7:25 ` [PATCH RFC v2 12/12] vfio/ccw: update sense data if a unit check is pending Dong Jia Shi
2017-01-12 7:25 ` [Qemu-devel] " Dong Jia Shi
2017-01-12 8:00 ` [Qemu-devel] [PATCH RFC v2 00/12] basic channel IO passthrough infrastructure based on vfio no-reply
2017-01-12 8:00 ` no-reply
2017-01-12 8:00 ` no-reply
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=20170217020815.GA28001@bjsdjshi@linux.vnet.ibm.com \
--to=bjsdjshi@linux.vnet.ibm.com \
--cc=agraf@suse.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.vnet.ibm.com \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=renxiaof@linux.vnet.ibm.com \
--cc=wkywang@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.