From: Greg Kurz <groug@kaod.org>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH qemu v12] spapr: Implement Open Firmware client interface
Date: Mon, 21 Dec 2020 13:27:34 +0100 [thread overview]
Message-ID: <20201221132734.084df0e8@bahia.lan> (raw)
In-Reply-To: <f6d39e3e-e4e8-4397-b83a-9e51fd54c0d4@ozlabs.ru>
On Mon, 21 Dec 2020 23:06:40 +1100
Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
[...]
> > Thanks for the split. The VOF paths are now clearly identified in
> > the sPAPR code, and well guarded by a check on x-vof. Rest of the
> > patch looks good to me. I gave it a try with a stock fedora 33
> > kernel and initramfs and it booted really fast !
> >
> > With the checkpatch complaints addressed,
>
>
> They all are about the firmware, not QEMU ifself, do we enforce it for
> such things as firmwares too?
>
Well, apparently checkpatch does :)
More seriously, this code is being added to the QEMU source tree, not
like it is some foreign code imported as a git submodule, so I don't see
why regular QEMU coding style guidelines wouldn't apply ?
>
> >
> > Acked-by: Greg Kurz <groug@kaod.org>
> >
> > and
> >
> > Tested-by: Greg Kurz <groug@kaod.org>
>
>
> Thanks! Now I am thinking whether someone may want to use it for
> something else, like... dunno... ARM? :)
>
>
Well, Zoltan seemed to have some interest in using VOF for
presumably other PowerPC based boards IIUC.
Another future work could be to add enough support to be able
to start grub and boot from a virtio device. :)
Cheers,
--
Greg
prev parent reply other threads:[~2020-12-21 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 2:50 [PATCH qemu v12] spapr: Implement Open Firmware client interface Alexey Kardashevskiy
2020-12-18 2:57 ` no-reply
2020-12-18 14:04 ` Greg Kurz
2020-12-21 12:06 ` Alexey Kardashevskiy
2020-12-21 12:27 ` Greg Kurz [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=20201221132734.084df0e8@bahia.lan \
--to=groug@kaod.org \
--cc=aik@ozlabs.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 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.