qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, Amos Kong <akong@redhat.com>
Cc: kevin@koconnor.net, seabios@seabios.org, qemu-devel@nongnu.org,
	"KONRAD Frédéric" <fred.konrad@greensocs.com>
Subject: Re: [Qemu-devel] [PATCH] boot: fix path pattern of scsi device
Date: Tue, 28 May 2013 12:26:34 +0200	[thread overview]
Message-ID: <51A4865A.8080702@redhat.com> (raw)
In-Reply-To: <51A4659B.8060601@redhat.com>

On 05/28/13 10:06, Paolo Bonzini wrote:
> Il 28/05/2013 09:40, Amos Kong ha scritto:
>> bootindex parameter of scsi device doesn't work, it causes
>> by wrong pattern in seabios.
>>
>> qemu passes the following firmware dev_path to seabios:
>>  /pci@i0cf8/scsi@4/virtio-scsi-device/channel@0/disk@0,0
> 
> No, this is another unexpected change due to the virtio refactoring in
> QEMU.  The right fix is in QEMU, by adding a get_fw_dev_path
> implementation in hw/virtio/virtio-bus.c.
> 
> We fixed it already for migration paths, it should be easy to do the
> same for this.
> 
> Please Cc qemu-stable@nongnu.org when sending the QEMU patch.
> 
> Thanks,
> 
> Paolo

Ahhh. I was super confused by this patch initially.

Amos, when posting a patch to both lists, please add the project name to
the bracketed bag-of-tags in the subject, like

[SeaBIOS PATCH] boot: fix path pattern of scsi device

I saw this message first on qemu-devel, and until I noticed "src/boot.c"
I was kind of confused whom you want to adapt to whom, and in what
direction Paolo argues against it.

So, virtio refactoring in QEMU (care to name a commit or release?)
changed the OpenFirmware device path exported for virtio-scsi devices
under the boot order fw_cfg key. This patch intended to adapt SeaBIOS to
recognize the new OFW devpath. Under this approach I would have to
update QemuBootOrder.c in OVMF in parallel, so that it accepts both old
and new style OFW devpaths for virtio-scsi.

However Paolo says the new style OFW devpath should be fixed
(eliminated) in qemu, and consumers shouldn't notice any change in the
long term. And I won't have to change QemuBootOrder.c. Right?

Thanks!
Laszlo

  parent reply	other threads:[~2013-05-28 10:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28  7:40 [Qemu-devel] [PATCH] boot: fix path pattern of scsi device Amos Kong
2013-05-28  8:06 ` Paolo Bonzini
2013-05-28  9:35   ` Amos Kong
2013-05-28  9:45     ` Paolo Bonzini
2013-05-28 10:26   ` Laszlo Ersek [this message]
2013-05-28 10:31     ` Amos Kong

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=51A4865A.8080702@redhat.com \
    --to=lersek@redhat.com \
    --cc=akong@redhat.com \
    --cc=fred.konrad@greensocs.com \
    --cc=kevin@koconnor.net \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.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).