From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
James Hogan <james.hogan@imgtec.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
kvm-devel <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>,
Sanjay Lal <sanjayl@kymasys.com>,
Aurelien Jarno <aurelien@aurel32.net>,
Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v5 00/12] KVM Support for MIPS32 Processors
Date: Thu, 10 Jul 2014 14:47:22 +0200 [thread overview]
Message-ID: <53BE8B5A.4070404@redhat.com> (raw)
In-Reply-To: <CAFEAcA_N6_sDw6XOtcfOfsmNoJxdbpVES+rpdG-wu4R-EKydNQ@mail.gmail.com>
Il 10/07/2014 14:17, Peter Maydell ha scritto:
>
> More generally, there doesn't really seem to be provision in the
> KVM KVM_EXIT_MMIO API for returning "this access failed".
> I guess in theory userspace could do all the "figure out how
> to adjust CPU state to do exception entry and then run VCPU",
> but that seems like quite a lot of work which the kernel already
> knows how to do; is there some way to provide a simpler API
> that lets userspace just inform the kernel that it needs to
> fault the access?
There are 3 free padding bytes in struct kvm_run's mmio field. It's
possible to add a per-VM capability and have the kernel check one of
these bytes when the capability is set.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
James Hogan <james.hogan@imgtec.com>
Cc: kvm-devel <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Sanjay Lal <sanjayl@kymasys.com>,
Aurelien Jarno <aurelien@aurel32.net>,
Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v5 00/12] KVM Support for MIPS32 Processors
Date: Thu, 10 Jul 2014 14:47:22 +0200 [thread overview]
Message-ID: <53BE8B5A.4070404@redhat.com> (raw)
In-Reply-To: <CAFEAcA_N6_sDw6XOtcfOfsmNoJxdbpVES+rpdG-wu4R-EKydNQ@mail.gmail.com>
Il 10/07/2014 14:17, Peter Maydell ha scritto:
>
> More generally, there doesn't really seem to be provision in the
> KVM KVM_EXIT_MMIO API for returning "this access failed".
> I guess in theory userspace could do all the "figure out how
> to adjust CPU state to do exception entry and then run VCPU",
> but that seems like quite a lot of work which the kernel already
> knows how to do; is there some way to provide a simpler API
> that lets userspace just inform the kernel that it needs to
> fault the access?
There are 3 free padding bytes in struct kvm_run's mmio field. It's
possible to add a per-VM capability and have the kernel check one of
these bytes when the capability is set.
Paolo
next prev parent reply other threads:[~2014-07-10 12:47 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 22:10 [PATCH v5 00/12] KVM Support for MIPS32 Processors James Hogan
2014-06-17 22:10 ` [Qemu-devel] " James Hogan
2014-06-17 22:10 ` [PATCH v5 01/12] target-mips: Reset CPU timer consistently James Hogan
2014-06-17 22:10 ` [Qemu-devel] " James Hogan
2014-06-17 22:10 ` [PATCH v5 02/12] hw/mips/cputimer: Don't start periodic timer in KVM mode James Hogan
2014-06-17 22:10 ` [Qemu-devel] " James Hogan
2014-06-17 22:10 ` [PATCH v5 03/12] hw/mips: Add API to convert KVM guest KSEG0 <-> GPA James Hogan
2014-06-17 22:10 ` [Qemu-devel] " James Hogan
2014-06-17 22:10 ` [PATCH v5 04/12] target-mips: get_physical_address: Add defines for segment bases James Hogan
2014-06-17 22:10 ` [Qemu-devel] " James Hogan
2014-06-17 22:10 ` [PATCH v5 05/12] target-mips: get_physical_address: Add KVM awareness James Hogan
2014-06-17 22:10 ` [Qemu-devel] " James Hogan
2014-06-17 22:10 ` [PATCH v5 06/12] kvm: Allow arch to set sigmask length James Hogan
2014-06-17 22:10 ` [Qemu-devel] " James Hogan
2014-06-17 22:10 ` [PATCH v5 07/12] target-mips: kvm: Add main KVM support for MIPS James Hogan
2014-06-17 22:10 ` [Qemu-devel] " James Hogan
2014-06-17 22:10 ` [PATCH v5 08/12] target-mips: Call kvm_mips_reset_vcpu() from mips_cpu_reset() James Hogan
2014-06-17 22:10 ` [Qemu-devel] " James Hogan
2014-06-17 22:10 ` [PATCH v5 09/12] hw/mips: In KVM mode, inject IRQ2 (I/O) interrupts via ioctls James Hogan
2014-06-17 22:10 ` [Qemu-devel] " James Hogan
2014-06-17 22:10 ` [PATCH v5 10/12] hw/mips: malta: Add KVM support James Hogan
2014-06-17 22:10 ` [Qemu-devel] " James Hogan
2014-06-19 16:27 ` Aurelien Jarno
2014-06-19 16:27 ` [Qemu-devel] " Aurelien Jarno
2014-06-19 19:34 ` Sanjay Lal
2014-06-19 19:34 ` Sanjay Lal
2014-06-19 21:47 ` Aurelien Jarno
2014-06-19 21:47 ` Aurelien Jarno
2014-06-20 6:07 ` Paolo Bonzini
2014-06-20 6:07 ` [Qemu-devel] " Paolo Bonzini
2014-06-20 8:46 ` James Hogan
2014-06-20 8:46 ` James Hogan
2014-06-20 9:10 ` Aurelien Jarno
2014-06-20 9:10 ` Aurelien Jarno
2014-06-20 10:38 ` Paolo Bonzini
2014-06-20 10:38 ` Paolo Bonzini
2014-06-20 11:19 ` Aurelien Jarno
2014-06-20 11:19 ` Aurelien Jarno
2014-06-20 11:28 ` James Hogan
2014-06-20 11:28 ` James Hogan
2014-06-20 9:25 ` James Hogan
2014-06-20 9:25 ` James Hogan
2014-06-20 11:11 ` Paolo Bonzini
2014-06-20 11:11 ` Paolo Bonzini
2014-06-20 11:20 ` Aurelien Jarno
2014-06-20 11:20 ` [Qemu-devel] " Aurelien Jarno
2014-06-17 22:10 ` [PATCH v5 11/12] target-mips: Enable KVM support in build system James Hogan
2014-06-17 22:10 ` [Qemu-devel] " James Hogan
2014-06-17 22:10 ` [PATCH v5 12/12] MAINTAINERS: Add entry for MIPS KVM James Hogan
2014-06-17 22:10 ` [Qemu-devel] " James Hogan
2014-06-18 15:00 ` [PATCH v5 00/12] KVM Support for MIPS32 Processors Paolo Bonzini
2014-06-18 15:00 ` [Qemu-devel] " Paolo Bonzini
2014-06-19 16:29 ` Aurelien Jarno
2014-06-19 16:29 ` [Qemu-devel] " Aurelien Jarno
2014-07-10 12:17 ` Peter Maydell
2014-07-10 12:17 ` Peter Maydell
2014-07-10 12:47 ` Paolo Bonzini [this message]
2014-07-10 12:47 ` Paolo Bonzini
2014-07-14 13:33 ` James Hogan
2014-07-14 13:33 ` James Hogan
2014-07-14 14:35 ` Peter Maydell
2014-07-14 14:35 ` Peter Maydell
2014-07-14 15:50 ` James Hogan
2014-07-14 15:50 ` James Hogan
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=53BE8B5A.4070404@redhat.com \
--to=pbonzini@redhat.com \
--cc=aurelien@aurel32.net \
--cc=christoffer.dall@linaro.org \
--cc=gleb@redhat.com \
--cc=james.hogan@imgtec.com \
--cc=kvm@vger.kernel.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sanjayl@kymasys.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.