From: Li Qiang <liq3ea@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Li Qiang <liq3ea@163.com>, Jiri Slaby <jslaby@suse.cz>,
Paolo Bonzini <pbonzini@redhat.com>,
Qemu Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 1/3] edu: mmio: set 'max_access_size' to 8
Date: Mon, 22 Apr 2019 09:17:07 +0800 [thread overview]
Message-ID: <CAKXe6S+5TTO3Czxsx98rd3d5UvyCnd5gMeWE6RW8b_eeE_b+3Q@mail.gmail.com> (raw)
In-Reply-To: <46a216be-0898-2d52-485d-fd07428c8b76@redhat.com>
Philippe Mathieu-Daudé <philmd@redhat.com> 于2019年4月21日周日 下午6:28写道:
> Hi Li,
>
> The patch title is not very descriptive, maybe "allow 64-bit access"
>
>
> On 4/20/19 6:14 PM, Li Qiang wrote:
> > The edu spec said, the MMIO area can be accessed by 8 bytes.
>
> or 64-bit...
>
> > However currently the 'max_access_size' is not so the MMIO
> > access dispatch can only access 4 bytes one time. This patch
>
> 32-bit
>
> > fixes this to respect the spec.
> >
> > Notice: here the 'min_access_size' is not a must, I set this
> > for completement.
>
> Which one? valid/impl? I think you can drop this comment from the commit
> description.
>
>
Both needed. from memory_access_size, if we has no valid.max_access_size,
this function will set it to 4.
static int memory_access_size(MemoryRegion *mr, unsigned l, hwaddr addr)
{
unsigned access_size_max = mr->ops->valid.max_access_size;
/* Regions are assumed to support 1-4 byte accesses unless
otherwise specified. */
if (access_size_max == 0) {
access_size_max = 4;
}
...
}
>From access_with_adjusted_size, if we has no impl.max_access_size,
this function will set it to 4.
ps: I will appreciate if anyone can explain what's the meaning of valid and
impl's min/max_access_size
and how it affects the behavior.
Thanks,
Li Qiang
>
> > Signed-off-by: Li Qiang <liq3ea@163.com>
> > ---
> > hw/misc/edu.c | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/hw/misc/edu.c b/hw/misc/edu.c
> > index 91af452c9e..65fc32b928 100644
> > --- a/hw/misc/edu.c
> > +++ b/hw/misc/edu.c
> > @@ -289,6 +289,15 @@ static const MemoryRegionOps edu_mmio_ops = {
> > .read = edu_mmio_read,
> > .write = edu_mmio_write,
> > .endianness = DEVICE_NATIVE_ENDIAN,
> > + .valid = {
> > + .min_access_size = 4,
>
> Per the spec, this is correct.
>
> > + .max_access_size = 8,
>
> Correct.
>
> > + },
> > + .impl = {
> > + .min_access_size = 4,
>
> OK.
>
> > + .max_access_size = 8,
>
> Correct.
>
> > + },
> > +
> > };
> >
> > /*
> >
>
> With title/description updated:
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Li Qiang <liq3ea@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Jiri Slaby <jslaby@suse.cz>, Li Qiang <liq3ea@163.com>,
Qemu Developers <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/3] edu: mmio: set 'max_access_size' to 8
Date: Mon, 22 Apr 2019 09:17:07 +0800 [thread overview]
Message-ID: <CAKXe6S+5TTO3Czxsx98rd3d5UvyCnd5gMeWE6RW8b_eeE_b+3Q@mail.gmail.com> (raw)
Message-ID: <20190422011707.XFwqydd6XaeXlW1iPbbufuTQTNq2WO1FBWOXoIM57y0@z> (raw)
In-Reply-To: <46a216be-0898-2d52-485d-fd07428c8b76@redhat.com>
Philippe Mathieu-Daudé <philmd@redhat.com> 于2019年4月21日周日 下午6:28写道:
> Hi Li,
>
> The patch title is not very descriptive, maybe "allow 64-bit access"
>
>
> On 4/20/19 6:14 PM, Li Qiang wrote:
> > The edu spec said, the MMIO area can be accessed by 8 bytes.
>
> or 64-bit...
>
> > However currently the 'max_access_size' is not so the MMIO
> > access dispatch can only access 4 bytes one time. This patch
>
> 32-bit
>
> > fixes this to respect the spec.
> >
> > Notice: here the 'min_access_size' is not a must, I set this
> > for completement.
>
> Which one? valid/impl? I think you can drop this comment from the commit
> description.
>
>
Both needed. from memory_access_size, if we has no valid.max_access_size,
this function will set it to 4.
static int memory_access_size(MemoryRegion *mr, unsigned l, hwaddr addr)
{
unsigned access_size_max = mr->ops->valid.max_access_size;
/* Regions are assumed to support 1-4 byte accesses unless
otherwise specified. */
if (access_size_max == 0) {
access_size_max = 4;
}
...
}
From access_with_adjusted_size, if we has no impl.max_access_size,
this function will set it to 4.
ps: I will appreciate if anyone can explain what's the meaning of valid and
impl's min/max_access_size
and how it affects the behavior.
Thanks,
Li Qiang
>
> > Signed-off-by: Li Qiang <liq3ea@163.com>
> > ---
> > hw/misc/edu.c | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/hw/misc/edu.c b/hw/misc/edu.c
> > index 91af452c9e..65fc32b928 100644
> > --- a/hw/misc/edu.c
> > +++ b/hw/misc/edu.c
> > @@ -289,6 +289,15 @@ static const MemoryRegionOps edu_mmio_ops = {
> > .read = edu_mmio_read,
> > .write = edu_mmio_write,
> > .endianness = DEVICE_NATIVE_ENDIAN,
> > + .valid = {
> > + .min_access_size = 4,
>
> Per the spec, this is correct.
>
> > + .max_access_size = 8,
>
> Correct.
>
> > + },
> > + .impl = {
> > + .min_access_size = 4,
>
> OK.
>
> > + .max_access_size = 8,
>
> Correct.
>
> > + },
> > +
> > };
> >
> > /*
> >
>
> With title/description updated:
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>
>
next prev parent reply other threads:[~2019-04-22 1:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-20 16:14 [Qemu-devel] [PATCH v2 0/3] hw: edu: some fixes Li Qiang
2019-04-20 16:14 ` Li Qiang
2019-04-20 16:14 ` [Qemu-devel] [PATCH v2 1/3] edu: mmio: set 'max_access_size' to 8 Li Qiang
2019-04-20 16:14 ` Li Qiang
2019-04-21 10:28 ` Philippe Mathieu-Daudé
2019-04-21 10:28 ` Philippe Mathieu-Daudé
2019-04-22 1:17 ` Li Qiang [this message]
2019-04-22 1:17 ` Li Qiang
2019-04-22 16:27 ` Philippe Mathieu-Daudé
2019-04-22 16:27 ` Philippe Mathieu-Daudé
2019-04-23 3:50 ` Li Qiang
2019-04-23 3:50 ` Li Qiang
2019-04-20 16:14 ` [Qemu-devel] [PATCH v2 2/3] edu: mmio: allow mmio read dispatch accept 8 bytes Li Qiang
2019-04-20 16:14 ` Li Qiang
2019-04-21 10:44 ` Philippe Mathieu-Daudé
2019-04-21 10:44 ` Philippe Mathieu-Daudé
2019-04-22 1:22 ` Li Qiang
2019-04-22 1:22 ` Li Qiang
2019-04-20 16:14 ` [Qemu-devel] [PATCH v2 3/3] edu: uses uint64_t in dma operation Li Qiang
2019-04-20 16:14 ` Li Qiang
2019-04-21 10:32 ` Philippe Mathieu-Daudé
2019-04-21 10:32 ` Philippe Mathieu-Daudé
2019-04-22 1:21 ` Li Qiang
2019-04-22 1:21 ` Li Qiang
2019-04-22 16:29 ` Philippe Mathieu-Daudé
2019-04-22 16:29 ` Philippe Mathieu-Daudé
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=CAKXe6S+5TTO3Czxsx98rd3d5UvyCnd5gMeWE6RW8b_eeE_b+3Q@mail.gmail.com \
--to=liq3ea@gmail.com \
--cc=jslaby@suse.cz \
--cc=liq3ea@163.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--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).