From: <peng.hao2@zte.com.cn>
To: peter.maydell@linaro.org
Cc: drjones@redhat.com, philmd@redhat.com, qemu-devel@nongnu.org,
qemu-arm@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V7 4/6] hw/arm/virt: Use the pvpanic device
Date: Wed, 21 Nov 2018 16:00:04 +0800 (CST) [thread overview]
Message-ID: <201811211600040239948@zte.com.cn> (raw)
In-Reply-To: <CAFEAcA-u=_kq66ZxawHhGCjkKjCo=urw7W3GfOwYK00AMRfWjg@mail.gmail.com>
> > Add pvpanic device in arm virt machine.
> >
> > Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
> > Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> > ---
> > default-configs/arm-softmmu.mak | 1 +
> > hw/arm/virt.c | 21 +++++++++++++++++++++
> > include/hw/arm/virt.h | 1 +
> > 3 files changed, 23 insertions(+)
> >
> > diff --git a/default-configs/arm-softmmu.mak b/default-configs/arm-softmmu.mak
> > index 2420491..50345df 100644
> > --- a/default-configs/arm-softmmu.mak
> > +++ b/default-configs/arm-softmmu.mak
> > @@ -159,3 +159,4 @@ CONFIG_PCI_DESIGNWARE=y
> > CONFIG_STRONGARM=y
> > CONFIG_HIGHBANK=y
> > CONFIG_MUSICPAL=y
> > +CONFIG_PVPANIC=y
> > diff --git a/hw/arm/virt.c b/hw/arm/virt.c
> > index 9f67782..c4f29c8 100644
[...]
> > + "compatible", "qemu,pvpanic-mmio");
> > + qemu_fdt_setprop_sized_cells(vms->fdt, nodename, "reg",
> > + 2, base, 2, size);
>
> Note that we can't take these patches into QEMU until the device
> tree binding has been agreed upstream and accepted into the kernel.
>
kernel part : https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/log/?h=char-misc-next
> > + g_free(nodename);
> > +}
> > +
> > static void create_fdt(VirtMachineState *vms)
> > {
> > void *fdt = create_device_tree(&vms->fdt_size);
> > @@ -1531,6 +1550,8 @@ static void machvirt_init(MachineState *machine)
> >
> > create_flash(vms, sysmem, secure_sysmem ? secure_sysmem : sysmem);
> >
> > + create_pvpanic_device(vms);
> > +
> > create_gic(vms, pic);
>
> As Shannon suggests, we should not be creating this device by default.
I'm just working for that.
Thanks.
>
> thanks
> -- PMM
next prev parent reply other threads:[~2018-11-21 8:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 10:50 [Qemu-devel] [PATCH V7 0/5] add pvpanic mmio support Peng Hao
2018-11-16 10:50 ` [Qemu-devel] [PATCH V7 1/6] hw/misc/pvpanic: Build the pvpanic device in $(common-obj) Peng Hao
2018-11-20 14:22 ` Peter Maydell
2018-11-16 10:50 ` [Qemu-devel] [PATCH V7 2/6] hw/misc/pvpanic: Cosmetic renaming Peng Hao
2018-11-16 10:50 ` [Qemu-devel] [PATCH V7 3/6] hw/misc/pvpanic: Add the MMIO interface Peng Hao
2018-11-20 14:29 ` Peter Maydell
2018-11-16 10:50 ` [Qemu-devel] [PATCH V7 4/6] hw/arm/virt: Use the pvpanic device Peng Hao
2018-11-16 3:29 ` [Qemu-devel] [Qemu-arm] " Shannon Zhao
2018-11-16 4:31 ` peng.hao2
2018-11-20 14:32 ` [Qemu-devel] " Peter Maydell
2018-11-21 8:00 ` peng.hao2 [this message]
2018-11-16 10:50 ` [Qemu-devel] [PATCH V7 5/6] hw/arm/virt: add pvpanic device in virt acpi table Peng Hao
2018-11-16 10:50 ` [Qemu-devel] [PATCH V7 6/6] pvpanic : update pvpanic document Peng Hao
2018-11-16 9:29 ` Andrew Jones
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=201811211600040239948@zte.com.cn \
--to=peng.hao2@zte.com.cn \
--cc=drjones@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.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).