From: Christoffer Dall <christoffer.dall@linaro.org>
To: "Jérémy Fanguède" <j.fanguede@virtualopensystems.com>
Cc: kvmarm@lists.cs.columbia.edu, Paolo Bonzini <pbonzini@redhat.com>,
linux-arm-kernel@lists.infradead.org,
"open list:Overall" <kvm@vger.kernel.org>,
QEMU Developers <qemu-devel@nongnu.org>,
VirtualOpenSystems Technical Team <tech@virtualopensystems.com>
Subject: Re: [RFC] ARM/ARM64: KVM: Implement KVM_FLUSH_DCACHE_GPA ioctl
Date: Thu, 7 May 2015 13:20:27 +0200 [thread overview]
Message-ID: <20150507112027.GC25885@cbox> (raw)
In-Reply-To: <CAGE1QJrabWWs0O1V-MpOxT_=1472TXb5rvJzJAJNfWH70x9pcg@mail.gmail.com>
On Thu, May 07, 2015 at 12:50:50PM +0200, Jérémy Fanguède wrote:
> On Wed, May 6, 2015 at 4:12 PM, Christoffer Dall
> <christoffer.dall@linaro.org> wrote:
> > Hi Jérémy,
> >
> > On Tue, May 05, 2015 at 11:13:11AM +0200, Jérémy Fanguède wrote:
> >> To maintain cache coherency on ARM, we may need a mechanism to flush
> >> the data cache.
> >
> > In addition to generally just making this functionality available (see
> > below), do you have an actual use case in mind for this? To solve the
> > VGA issue, for example, we already have a patch series from Drew trying
> > to address this. Does that not work for you?
> >
> > There was a long discussion about this here:
> > https://lists.cs.columbia.edu/pipermail/kvmarm/2015-February/013593.html
> >
> > Drew then created a patch set, here:
> > https://lists.nongnu.org/archive/html/qemu-devel/2015-03/msg01254.html
> >
> > and replied to himself, here:
> > https://www.marc.info/?l=android-virt&m=142670523929132&w=3
> >
> > Which basically says that he doesn't like having to do flushes all over
> > QEMU (IIUC), so he sent this version instead:
> > https://lists.cs.columbia.edu/pipermail/kvmarm/2015-March/014027.html
> >
> > Which he now said he'd respin.
>
> In fact, I used this ioctl in pairs with this QEMU patch series:
> https://lists.nongnu.org/archive/html/qemu-devel/2015-05/msg00407.html
> My current work doesn't do anything about vga ram, so vga issue
> probably still persists, but it solves others issues with some
> emulated devices (mainly PCI) which were failing before and now work
> fine with this patch.
Why does Drew's approach not work and your approach works here? What is
the case that we haven't though about yet?
-Christoffer
WARNING: multiple messages have this Message-ID (diff)
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] ARM/ARM64: KVM: Implement KVM_FLUSH_DCACHE_GPA ioctl
Date: Thu, 7 May 2015 13:20:27 +0200 [thread overview]
Message-ID: <20150507112027.GC25885@cbox> (raw)
In-Reply-To: <CAGE1QJrabWWs0O1V-MpOxT_=1472TXb5rvJzJAJNfWH70x9pcg@mail.gmail.com>
On Thu, May 07, 2015 at 12:50:50PM +0200, J?r?my Fangu?de wrote:
> On Wed, May 6, 2015 at 4:12 PM, Christoffer Dall
> <christoffer.dall@linaro.org> wrote:
> > Hi J?r?my,
> >
> > On Tue, May 05, 2015 at 11:13:11AM +0200, J?r?my Fangu?de wrote:
> >> To maintain cache coherency on ARM, we may need a mechanism to flush
> >> the data cache.
> >
> > In addition to generally just making this functionality available (see
> > below), do you have an actual use case in mind for this? To solve the
> > VGA issue, for example, we already have a patch series from Drew trying
> > to address this. Does that not work for you?
> >
> > There was a long discussion about this here:
> > https://lists.cs.columbia.edu/pipermail/kvmarm/2015-February/013593.html
> >
> > Drew then created a patch set, here:
> > https://lists.nongnu.org/archive/html/qemu-devel/2015-03/msg01254.html
> >
> > and replied to himself, here:
> > https://www.marc.info/?l=android-virt&m=142670523929132&w=3
> >
> > Which basically says that he doesn't like having to do flushes all over
> > QEMU (IIUC), so he sent this version instead:
> > https://lists.cs.columbia.edu/pipermail/kvmarm/2015-March/014027.html
> >
> > Which he now said he'd respin.
>
> In fact, I used this ioctl in pairs with this QEMU patch series:
> https://lists.nongnu.org/archive/html/qemu-devel/2015-05/msg00407.html
> My current work doesn't do anything about vga ram, so vga issue
> probably still persists, but it solves others issues with some
> emulated devices (mainly PCI) which were failing before and now work
> fine with this patch.
Why does Drew's approach not work and your approach works here? What is
the case that we haven't though about yet?
-Christoffer
WARNING: multiple messages have this Message-ID (diff)
From: Christoffer Dall <christoffer.dall@linaro.org>
To: "Jérémy Fanguède" <j.fanguede@virtualopensystems.com>
Cc: "open list:Overall" <kvm@vger.kernel.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [Qemu-devel] [RFC] ARM/ARM64: KVM: Implement KVM_FLUSH_DCACHE_GPA ioctl
Date: Thu, 7 May 2015 13:20:27 +0200 [thread overview]
Message-ID: <20150507112027.GC25885@cbox> (raw)
In-Reply-To: <CAGE1QJrabWWs0O1V-MpOxT_=1472TXb5rvJzJAJNfWH70x9pcg@mail.gmail.com>
On Thu, May 07, 2015 at 12:50:50PM +0200, Jérémy Fanguède wrote:
> On Wed, May 6, 2015 at 4:12 PM, Christoffer Dall
> <christoffer.dall@linaro.org> wrote:
> > Hi Jérémy,
> >
> > On Tue, May 05, 2015 at 11:13:11AM +0200, Jérémy Fanguède wrote:
> >> To maintain cache coherency on ARM, we may need a mechanism to flush
> >> the data cache.
> >
> > In addition to generally just making this functionality available (see
> > below), do you have an actual use case in mind for this? To solve the
> > VGA issue, for example, we already have a patch series from Drew trying
> > to address this. Does that not work for you?
> >
> > There was a long discussion about this here:
> > https://lists.cs.columbia.edu/pipermail/kvmarm/2015-February/013593.html
> >
> > Drew then created a patch set, here:
> > https://lists.nongnu.org/archive/html/qemu-devel/2015-03/msg01254.html
> >
> > and replied to himself, here:
> > https://www.marc.info/?l=android-virt&m=142670523929132&w=3
> >
> > Which basically says that he doesn't like having to do flushes all over
> > QEMU (IIUC), so he sent this version instead:
> > https://lists.cs.columbia.edu/pipermail/kvmarm/2015-March/014027.html
> >
> > Which he now said he'd respin.
>
> In fact, I used this ioctl in pairs with this QEMU patch series:
> https://lists.nongnu.org/archive/html/qemu-devel/2015-05/msg00407.html
> My current work doesn't do anything about vga ram, so vga issue
> probably still persists, but it solves others issues with some
> emulated devices (mainly PCI) which were failing before and now work
> fine with this patch.
Why does Drew's approach not work and your approach works here? What is
the case that we haven't though about yet?
-Christoffer
next prev parent reply other threads:[~2015-05-07 11:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 9:13 [RFC] ARM/ARM64: KVM: Implement KVM_FLUSH_DCACHE_GPA ioctl Jérémy Fanguède
2015-05-05 9:13 ` [Qemu-devel] " Jérémy Fanguède
2015-05-05 9:13 ` Jérémy Fanguède
2015-05-06 14:12 ` Christoffer Dall
2015-05-06 14:12 ` [Qemu-devel] " Christoffer Dall
2015-05-06 14:12 ` Christoffer Dall
2015-05-07 10:50 ` Jérémy Fanguède
2015-05-07 10:50 ` [Qemu-devel] " Jérémy Fanguède
2015-05-07 10:50 ` Jérémy Fanguède
2015-05-07 11:20 ` Christoffer Dall [this message]
2015-05-07 11:20 ` [Qemu-devel] " Christoffer Dall
2015-05-07 11:20 ` Christoffer Dall
2015-05-07 14:50 ` Jérémy Fanguède
2015-05-07 14:50 ` [Qemu-devel] " Jérémy Fanguède
2015-05-07 14:50 ` Jérémy Fanguède
2015-05-07 15:34 ` Christoffer Dall
2015-05-07 15:34 ` [Qemu-devel] " Christoffer Dall
2015-05-07 15:34 ` Christoffer Dall
2015-05-07 16:56 ` Jérémy Fanguède
2015-05-07 16:56 ` [Qemu-devel] " Jérémy Fanguède
2015-05-07 16:56 ` Jérémy Fanguède
2015-05-07 17:01 ` Paolo Bonzini
2015-05-07 17:01 ` [Qemu-devel] " Paolo Bonzini
2015-05-07 17:01 ` Paolo Bonzini
2015-05-15 11:43 ` Laszlo Ersek
2015-05-15 11:43 ` [Qemu-devel] " Laszlo Ersek
2015-05-15 11:43 ` Laszlo Ersek
2015-05-15 15:12 ` Christoffer Dall
2015-05-15 15:12 ` [Qemu-devel] " Christoffer Dall
2015-05-15 15:12 ` Christoffer Dall
2015-05-15 15:24 ` Paolo Bonzini
2015-05-15 15:24 ` [Qemu-devel] " Paolo Bonzini
2015-05-15 15:24 ` Paolo Bonzini
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=20150507112027.GC25885@cbox \
--to=christoffer.dall@linaro.org \
--cc=j.fanguede@virtualopensystems.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tech@virtualopensystems.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.