linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm/arm64: KVM: Fix unaligned access bug on gicv2 access
Date: Tue, 23 Sep 2014 16:03:16 +0200	[thread overview]
Message-ID: <CAMJs5B9729eASE9WgbqrG9oj1WJB8grvwugs22NGk1xyJ-v5MQ@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA8pYezWttDHRpoNYn0wWvHg5M2xQLE4-D84uDC37k8emQ@mail.gmail.com>

On Tue, Sep 23, 2014 at 4:01 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 23 September 2014 14:52, Christoffer Dall
> <christoffer.dall@linaro.org> wrote:
>> If anyone feels like reviewing my patch and giving it a quick test on a
>> BE system with a version of QEMU with the pl011 level-triggered patch,
>
> FWIW, any old version of QEMU running the vexpress-a15 model
> will also use level-triggered interrupts for pl011, because
> the upstream DTB which we use for that board has always
> correctly marked the pl011 and all the other motherboard
> devices as being level-triggered.
>
> I'm still not 100% convinced we shouldn't mark the
> virtio-mmio devices as level-triggered, incidentally.
> I *think* that (a) the spec pretty heavily implies that
> the lines behave as level triggered but (b) the
> specific text in the spec about required guest code
> to avoid races (s.2.4.2 of the 0.9.5 spec) means that
> even if the interrupt controller treats them as edge
> triggered it's OK.
>
I think we should really sit down and figure out the right thing to do
during KVM Forum if we can allocate a slot for that.  Marc seems to
also have some input he would like to share on this subject.

For the record, I'm fine with changing the virtio-mmio devices, but
it's probably worth quickly measuring the performance impact first.

Thanks,
-Christoffer

      reply	other threads:[~2014-09-23 14:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 21:12 [GIT PULL] Last-minute fix for kvm/arm64 Christoffer Dall
2014-09-22 21:12 ` [GIT PULL] arm/arm64: KVM: Fix unaligned access bug on gicv2 access Christoffer Dall
2014-09-22 22:07   ` Will Deacon
2014-09-23  8:36     ` Paolo Bonzini
2014-09-23 11:14       ` Christoffer Dall
2014-09-23 11:50         ` Paolo Bonzini
2014-09-23 12:44           ` Andre Przywara
2014-09-23 12:48             ` Paolo Bonzini
2014-09-23 13:52             ` Christoffer Dall
2014-09-23 13:52               ` Paolo Bonzini
2014-09-23 14:07                 ` Christoffer Dall
2014-09-23 14:01               ` Peter Maydell
2014-09-23 14:03                 ` Christoffer Dall [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=CAMJs5B9729eASE9WgbqrG9oj1WJB8grvwugs22NGk1xyJ-v5MQ@mail.gmail.com \
    --to=christoffer.dall@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).