All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
	qemu-s390x@nongnu.org,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Eric Farman <farman@linux.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] pc-bios/s390-ccw/virtio: Read device config after feature negotiation
Date: Thu, 23 Jun 2022 12:13:21 +0200	[thread overview]
Message-ID: <878rpn8z7i.fsf@redhat.com> (raw)
In-Reply-To: <749f88c5-379c-6284-f3c7-c8074191c8a9@redhat.com>

On Thu, Jun 23 2022, Thomas Huth <thuth@redhat.com> wrote:

> On 23/06/2022 10.44, Cornelia Huck wrote:
>> On Thu, Jun 23 2022, Thomas Huth <thuth@redhat.com> wrote:
>> 
>>> Feature negotiation should be done first, since some fields in the
>>> config area can depend on the negotiated features and thus should
>>> rather be read afterwards.
>> 
>> I suppose we don't negotiate any features that might affect the size of
>> the config space? Anyway, restricting ourselves to the minimum length
>> should be fine.
>
> Actually, even the virtio spec 0.9.5 already talks about 
> VIRTIO_BLK_F_BLK_SIZE and VIRTIO_BLK_F_GEOMETRY being necessary to get the 
> corresponding values in the config space ... so we're currently depending on 
> the good will of QEMU to also provide the values without these feature bits. 

Eww. The bad thing about QEMU being so relaxed is that you don't catch
issues like that... but if it works for now, there's at least no
pressure.

> I'm already thinking about providing a patch to properly request these 
> feature bits in the s390-ccw bios ... but the whole code there is so ugly 
> that I need some time to think about the right steps to clean it up first.

It's not ugly, it has grown organically :) (just like that overgrown
spot in my garden ;)



      reply	other threads:[~2022-06-23 10:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  7:11 [PATCH 0/2] pc-bios/s390-ccw: Two fixes for the virtio initialization Thomas Huth
2022-06-23  7:11 ` [PATCH 1/2] pc-bios/s390-ccw/virtio: Set missing status bits while initializing Thomas Huth
2022-06-23  7:59   ` Christian Borntraeger
2022-06-23  8:37   ` Cornelia Huck
2022-06-23 13:50   ` Eric Farman
2022-06-23  7:11 ` [PATCH 2/2] pc-bios/s390-ccw/virtio: Read device config after feature negotiation Thomas Huth
2022-06-23  8:44   ` Cornelia Huck
2022-06-23  9:55     ` Thomas Huth
2022-06-23 10:13       ` Cornelia Huck [this message]

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=878rpn8z7i.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=farman@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.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 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.