From: Paolo Bonzini <pbonzini@redhat.com>
To: Gavin Shan <gshan@redhat.com>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org
Cc: peter.maydell@linaro.org, maz@kernel.org, shan.gavin@gmail.com,
marcandre.lureau@redhat.com
Subject: Re: [PATCH] hw/char/pl011: Enable TxFIFO and async transmission
Date: Fri, 21 Feb 2020 09:25:53 +0100 [thread overview]
Message-ID: <12b3d4d4-736b-e861-6b6b-5b6885b7cbf1@redhat.com> (raw)
In-Reply-To: <20200221044908.266883-1-gshan@redhat.com>
On 21/02/20 05:49, Gavin Shan wrote:
> @@ -306,6 +362,7 @@ static const VMStateDescription vmstate_pl011 = {
> VMSTATE_UINT32(int_enabled, PL011State),
> VMSTATE_UINT32(int_level, PL011State),
> VMSTATE_UINT32_ARRAY(read_fifo, PL011State, 16),
> + VMSTATE_UINT8_ARRAY(write_fifo, PL011State, 16),
> VMSTATE_UINT32(ilpr, PL011State),
> VMSTATE_UINT32(ibrd, PL011State),
> VMSTATE_UINT32(fbrd, PL011State),
> @@ -313,6 +370,7 @@ static const VMStateDescription vmstate_pl011 = {
> VMSTATE_INT32(read_pos, PL011State),
> VMSTATE_INT32(read_count, PL011State),
> VMSTATE_INT32(read_trigger, PL011State),
> + VMSTATE_INT32(write_count, PL011State),
Hi Gavin, please add these two fields to a subsection, so that they are
emitted only if write_count > 0.
Thanks!
Paolo
> VMSTATE_END_OF_LIST()
> }
> };
> diff --git a/include/hw/char/pl011.h b/include/hw/char/pl011.h
> index 14187165c6..aeaf332eca 100644
> --- a/include/hw/char/pl011.h
> +++ b/include/hw/char/pl011.h
> @@ -38,6 +38,7 @@ typedef struct PL011State {
> uint32_t int_enabled;
> uint32_t int_level;
> uint32_t read_fifo[16];
> + uint8_t write_fifo[16];
> uint32_t ilpr;
> uint32_t ibrd;
> uint32_t fbrd;
> @@ -45,6 +46,7 @@ typedef struct PL011State {
> int read_pos;
> int read_count;
> int read_trigger;
> + int write_count;
> CharBackend chr;
> qemu_irq irq[6];
> const unsigned char *id;
>
next prev parent reply other threads:[~2020-02-21 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 4:49 [PATCH] hw/char/pl011: Enable TxFIFO and async transmission Gavin Shan
2020-02-21 6:28 ` no-reply
2020-02-21 9:37 ` Philippe Mathieu-Daudé
2020-02-21 9:46 ` Philippe Mathieu-Daudé
2020-02-24 3:42 ` Gavin Shan
2020-02-21 8:25 ` Paolo Bonzini [this message]
2020-02-21 8:56 ` Gavin Shan
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=12b3d4d4-736b-e861-6b6b-5b6885b7cbf1@redhat.com \
--to=pbonzini@redhat.com \
--cc=gshan@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=maz@kernel.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shan.gavin@gmail.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).