From: <peng.hao2@zte.com.cn>
To: philmd@redhat.com, peter.maydell@linaro.org
Cc: qemu-devel@nongnu.org, wency@cn.fujitsu.com, hutao@cn.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH v3 0/4] hw/misc: Add a MMIO interface to the pvpanicdevice
Date: Thu, 25 Oct 2018 13:47:12 +0800 (CST) [thread overview]
Message-ID: <201810251347121915659@zte.com.cn> (raw)
In-Reply-To: <43045a7f-4092-c039-af58-6221db22d3f4@redhat.com>
>On 18/10/2018 15:04, Philippe Mathieu-Daudé wrote:
>> Hi, this series takes Peng Hao's previous work but rather than adding yet
>> another device, simply add the MMIO interface to the current device (which
>> only implements the I/O port access).
>>
>> The first patches are simple cleanups:
>> - patch 1 move the pvpanic device with the 'ocmmon objects' so we compile
>> it once for the x86/arm/aarch64 archs,
>> - patch 2 simply renames ISA fields/definitions to generic ones.
>>
>> Then instead of add/use the MMIO pvpanic device in the virt machine in an
>> unique patch, I split it in two distinct patches:
>> - patch 3 uses Peng Hao's work, but add the MMIO interface to the existing
>> device (no logical change).
>> - patch 4 is Peng Hao's work in the virt machine (no logical change).
>>
>> v2 from Peng Hao is:
>> https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg03433.html
>>
>> Regards,
>>
>> Phil.
>>
>> Philippe Mathieu-Daudé (4):
>> hw/misc/pvpanic: Build the pvpanic device in $(common-obj)
>> hw/misc/pvpanic: Cosmetic renaming
>
>Oops I failed when rebasing, these two are supposed to be from
>
>Peng Hao
>
now it can works.
In refactoring code, there is still a need to add a type to distinguish different bus device.
I add a type TYPE_PVPANIC_MMIO for sysbus pvpanic device and
orignal TYPE_PVPANIC for isa pvpanic deivce.
bindling-DT "qemu,pvpanic-mmio" in kernel is in review.
I will resubmit patches.
Thanks.
>with below my S-o-b:
>[PMD: Use TYPE_PVPANIC definition, split in 2 patches,
>improved patch subject]
>
>> hw/misc/pvpanic: Add the MMIO interface
>> hw/arm/virt: Use the pvpanic device
>>
>> default-configs/arm-softmmu.mak | 2 +-
>> hw/arm/virt.c | 21 ++++++++++
>> hw/misc/Makefile.objs | 2 +-
>> hw/misc/pvpanic.c | 68 +++++++++++++++++++++++++++++----
>> include/hw/arm/virt.h | 1 +
>> 5 files changed, 84 insertions(+), 10 deletions(-)
>>
prev parent reply other threads:[~2018-10-25 5:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 13:04 [Qemu-devel] [PATCH v3 0/4] hw/misc: Add a MMIO interface to the pvpanic device Philippe Mathieu-Daudé
2018-10-18 13:04 ` [Qemu-devel] [PATCH v3 1/4] hw/misc/pvpanic: Build the pvpanic device in $(common-obj) Philippe Mathieu-Daudé
2018-10-18 13:04 ` [Qemu-devel] [PATCH v3 2/4] hw/misc/pvpanic: Cosmetic renaming Philippe Mathieu-Daudé
2018-10-18 13:04 ` [Qemu-devel] [PATCH v3 3/4] hw/misc/pvpanic: Add the MMIO interface Philippe Mathieu-Daudé
2018-10-18 13:08 ` Peter Maydell
2018-10-18 13:19 ` Philippe Mathieu-Daudé
2018-10-18 13:27 ` Peter Maydell
2018-10-18 16:13 ` peng.hao2
2018-10-18 13:04 ` [Qemu-devel] [PATCH v3 4/4] hw/arm/virt: Use the pvpanic device Philippe Mathieu-Daudé
2018-10-18 13:37 ` Peter Maydell
2018-10-18 16:07 ` peng.hao2
2018-10-18 13:09 ` [Qemu-devel] [PATCH v3 0/4] hw/misc: Add a MMIO interface to " Philippe Mathieu-Daudé
2018-10-25 5:47 ` peng.hao2 [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=201810251347121915659@zte.com.cn \
--to=peng.hao2@zte.com.cn \
--cc=hutao@cn.fujitsu.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wency@cn.fujitsu.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 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).