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 V10 7/9] hw/misc/pvpanic: preparing for adding configure interface
Date: Sat, 1 Dec 2018 17:11:55 +0800 (CST) [thread overview]
Message-ID: <201812011711555606300@zte.com.cn> (raw)
In-Reply-To: <CAFEAcA83C_Eic3K4yY5bGeEKJpY2uf26diFtDJ5r+W71jcX2DQ@mail.gmail.com>
>On Wed, 28 Nov 2018 at 03:50, Peng Hao <peng.hao2@zte.com.cn> wrote:
>>
>> Prepare for pvpanic-mmio configure interface.
>>
>> Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
>> ---
>> hw/arm/sysbus-fdt.c | 2 ++
>> hw/arm/virt.c | 2 ++
>> hw/misc/pvpanic.c | 11 +++++++++--
>> 3 files changed, 13 insertions(+), 2 deletions(-)
>
>This looks rather odd. The sysbus-fdt.c code is for
>handling devices that we must pass through from the
>host system (including pulling in device tree fragments
>from the host). The pvpanic device isn't a host pass
>through device so I don't think it should be touching
>that code at all. It's just a simple MMIO device.
>
>I suspect the reason you've done this is that you're
>trying to get "-device pvpanic" to work on the command
>line. I recommend not trying to get that to work.
>MMIO devices are not pluggable devices, and -device
>is not expected to work with them.
>
yes, I use -device pvpanic-mmio. Thank you for pointing this out.
I also felt a little odd when I realized it. But I didn't think about the reason.
I think I can use a way like iommu, and I've thought about it in doing my
current way.
thanks.
>thanks
>-- PMM
next prev parent reply other threads:[~2018-12-01 9:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 12:12 [Qemu-devel] [PATCH V10 0/9] add pvpanic mmio support Peng Hao
2018-11-28 12:12 ` [Qemu-devel] [PATCH V10 1/9] hw/misc/pvpanic: Build the pvpanic device in $(common-obj) Peng Hao
2018-11-28 12:12 ` [Qemu-devel] [PATCH V10 2/9] hw/misc/pvpanic: Cosmetic renaming Peng Hao
2018-11-30 15:39 ` Peter Maydell
2018-11-28 12:12 ` [Qemu-devel] [PATCH V10 3/9] hw/misc/pvpanic: Add the MMIO interface Peng Hao
2018-11-30 15:41 ` Peter Maydell
2018-11-28 12:12 ` [Qemu-devel] [PATCH V10 4/9] hw/arm/virt: Use the pvpanic device Peng Hao
2018-11-30 15:48 ` Peter Maydell
2018-11-28 12:12 ` [Qemu-devel] [PATCH V10 5/9] hw/arm/virt: add pvpanic device in virt acpi table Peng Hao
2018-11-30 15:51 ` Peter Maydell
2018-11-30 16:06 ` Andrew Jones
2018-11-28 12:12 ` [Qemu-devel] [PATCH V10 6/9] hw/misc/pvpanic: add configure query interface Peng Hao
2018-11-28 12:12 ` [Qemu-devel] [PATCH V10 7/9] hw/misc/pvpanic: preparing for adding configure interface Peng Hao
2018-11-30 15:56 ` Peter Maydell
2018-11-30 15:57 ` Peter Maydell
2018-11-30 16:14 ` Andrew Jones
2018-11-30 16:21 ` Peter Maydell
2018-12-01 9:28 ` [Qemu-devel] [PATCH V10 7/9] hw/misc/pvpanic: preparing foradding " peng.hao2
2018-12-01 12:05 ` Peter Maydell
2018-12-01 9:11 ` peng.hao2 [this message]
2018-11-28 12:12 ` [Qemu-devel] [PATCH V10 8/9] hw/misc/pvpanic: realize the " Peng Hao
2018-11-30 15:53 ` Peter Maydell
2018-11-28 12:12 ` [Qemu-devel] [PATCH V10 9/9] pvpanic : update pvpanic document Peng Hao
2018-11-30 16:00 ` 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=201812011711555606300@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).