From: Alexander Graf <agraf@suse.de>
To: Cornelia Huck <cornelia.huck@de.ibm.com>,
Ming Lei <ming.lei@canonical.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/4] s390-virtio-bus: move common virtio properties to virtio s390 device class
Date: Tue, 17 Jun 2014 14:06:25 +0200 [thread overview]
Message-ID: <53A02F41.7000908@suse.de> (raw)
In-Reply-To: <20140617140413.42c0b518.cornelia.huck@de.ibm.com>
On 17.06.14 14:04, Cornelia Huck wrote:
> On Tue, 17 Jun 2014 18:45:09 +0800
> Ming Lei <ming.lei@canonical.com> wrote:
>
>> On Tue, Jun 17, 2014 at 6:40 PM, Ming Lei <ming.lei@canonical.com> wrote:
>>> On Tue, Jun 17, 2014 at 6:25 PM, Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
>>>> On Tue, 17 Jun 2014 18:15:39 +0800
>>>> Ming Lei <ming.lei@canonical.com> wrote:
>>>>
>>>>> On Tue, Jun 17, 2014 at 4:46 PM, Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
>>>>>>> Looks like s390 virtio-blk never enables the two common features, is
>>>>>>> there any reason the two features can't be supported by s390?
>>>>>> Indirect descriptors are fine. event_idx will not work IIUC because we
>>>>>> always need to do a sync before we see changes, and this needs an
>>>>>> interrupt to trigger.
>>>>> Sounds like the old s390 isn't cache coherent? Because you mean
>>>>> write in one side can only be observed from another side with an
>>>>> explicit notification or interrupt.
>>>>>
>>>>> On arm/arm64, we didn't see any problem with event_idx.
>>>> But you probably have the queues in guest memory, as on other
>>>> transports (including virtio-ccw)? The old s390-virtio transport keeps
>>>> the devices and their virtqueues in a memory area behind the guest
>>>> memory - the guest does not see that memory directly, but a sync has to
>>>> be performed to see virtqueue movement (see s390_virtio_device_sync()).
>>> OK, it looks like a real physical device, :-)
>>>
>>> I will keep s390-virtio as it is, thanks for your explanation.
>> BTW, do you want me to add DEFINE_VIRTIO_COMMON_FEATURES()
>> to s390_virtio_net_properties and s390_virtio_scsi_properties since
>> I remove them from their default properties?
> It might be better to remove them for good :)
>
> Nobody has probably tried to use them for some time...
> I just start a very minimal guest with a virtio-console and a
> virtio-blk device. Don't know whether Alex has a more advanced setup
> at hand?
It's the only target that works with TCG, no?
Alex
next prev parent reply other threads:[~2014-06-17 12:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 15:40 [Qemu-devel] [PATCH 0/4] virtio: move common virtio properties to bus class device Ming Lei
2014-06-16 15:40 ` [Qemu-devel] [PATCH 1/4] virtio-pci: move common virtio properties to virtio-pci " Ming Lei
2014-06-16 15:40 ` [Qemu-devel] [PATCH 2/4] s390-virtio-bus: move common virtio properties to virtio s390 device class Ming Lei
2014-06-16 16:04 ` Cornelia Huck
2014-06-16 16:19 ` Ming Lei
2014-06-17 2:44 ` Ming Lei
2014-06-17 7:07 ` Cornelia Huck
2014-06-17 7:44 ` Cornelia Huck
2014-06-17 7:44 ` Ming Lei
2014-06-17 8:46 ` Cornelia Huck
2014-06-17 10:15 ` Ming Lei
2014-06-17 10:25 ` Cornelia Huck
2014-06-17 10:40 ` Ming Lei
2014-06-17 10:45 ` Ming Lei
2014-06-17 12:04 ` Cornelia Huck
2014-06-17 12:06 ` Alexander Graf [this message]
2014-06-17 12:56 ` Cornelia Huck
2014-06-17 12:57 ` Alexander Graf
2014-06-16 15:40 ` [Qemu-devel] [PATCH 3/4] s390 virtio-ccw: move common virtio properties to virtio ccw " Ming Lei
2014-06-16 16:01 ` Cornelia Huck
2014-06-16 15:40 ` [Qemu-devel] [PATCH 4/4] virtio-blk: remove DEFINE_VIRTIO_BLK_FEATURES Ming Lei
2014-06-16 15:44 ` [Qemu-devel] [PATCH 0/4] virtio: move common virtio properties to bus class device Paolo Bonzini
2014-06-16 16:02 ` Ming Lei
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=53A02F41.7000908@suse.de \
--to=agraf@suse.de \
--cc=cornelia.huck@de.ibm.com \
--cc=ming.lei@canonical.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).