From: Peter Maydell <peter.maydell@linaro.org>
To: Auger Eric <eric.auger@redhat.com>
Cc: Shannon Zhao <shannon.zhaosl@gmail.com>,
qemu-arm <qemu-arm@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Shannon Zhao <zhaoshenglong@huawei.com>
Subject: Re: [Qemu-devel] [PATCH V3 2/2] arm_gicv3_kvm: kvm_dist_get/put: skip the registers banked by GICR
Date: Thu, 24 May 2018 15:58:18 +0100 [thread overview]
Message-ID: <CAFEAcA-ffKgP30kPm=rWqMv4CewGRqu_WEcpwqGp+hqZzwhn-g@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA9oCppg2C32vd3YKKmvfO7n1KnFeXG14CV7UHcZpxcTqA@mail.gmail.com>
On 24 May 2018 at 15:56, Peter Maydell <peter.maydell@linaro.org> wrote:
> Oops, yes, you're right. My explanation applies to the
> various other bitmaps, where we are accessing the
> fields in the data structure using gic_bmp_ptr32(bmp, irq),
> but not to gicd_ipriority[], which we are directly accessing
> starting with the first word, not by indexing via bmp[irq].
>
> So we need to handle these two cases differently.
> You're correct that for gicd_ipriority[], the code in
> master reads and writes to that data structure as:
> [0, 0, ..., 0, irq 32, irq 33, ..., 0, 0, ... 0]
> so all the values are in the right place but we:
> (a) unnecessarily read/write zeroes for the PPI/SGI fields
> (b) fail to transfer the last 32 interrupts
>
> We can fix the gicd_ipriority[] case simply by adding
> bmp = GIC_INTERNAL;
Oops, I meant
bmp += GIC_INTERNAL;
thanks
-- PMM
next prev parent reply other threads:[~2018-05-24 14:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 3:53 [Qemu-devel] [PATCH V3 1/2] arm_gicv3_kvm: increase clroffset accordingly Shannon Zhao
2018-05-23 3:53 ` [Qemu-devel] [PATCH V3 2/2] arm_gicv3_kvm: kvm_dist_get/put: skip the registers banked by GICR Shannon Zhao
2018-05-24 9:04 ` Auger Eric
2018-05-24 9:20 ` Shannon Zhao
2018-05-24 12:10 ` Auger Eric
2018-05-24 13:14 ` Peter Maydell
2018-05-24 13:59 ` Auger Eric
2018-05-24 14:16 ` Peter Maydell
2018-05-24 14:40 ` Auger Eric
2018-05-24 14:56 ` Peter Maydell
2018-05-24 14:58 ` Peter Maydell [this message]
2018-05-24 15:09 ` Auger Eric
2018-05-25 8:42 ` Shannon Zhao
2018-05-25 9:00 ` Peter Maydell
2018-05-24 13:11 ` Peter Maydell
2018-05-25 9:15 ` Shannon Zhao
2018-05-24 12:38 ` [Qemu-devel] [PATCH V3 1/2] arm_gicv3_kvm: increase clroffset accordingly Peter Maydell
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='CAFEAcA-ffKgP30kPm=rWqMv4CewGRqu_WEcpwqGp+hqZzwhn-g@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=eric.auger@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhaosl@gmail.com \
--cc=zhaoshenglong@huawei.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).