From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: KVM list <kvm@vger.kernel.org>, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 03/15] KVM: Add compat ioctl for KVM_SET_SIGNAL_MASK
Date: Sun, 19 Jun 2011 16:01:22 +0300 [thread overview]
Message-ID: <4DFDF322.4060805@redhat.com> (raw)
In-Reply-To: <3B37E55B-D774-4E96-AA3C-7A550036C8A2@suse.de>
On 06/19/2011 03:53 PM, Alexander Graf wrote:
> On 19.06.2011, at 11:04, Avi Kivity wrote:
>
> > On 06/17/2011 05:49 PM, Alexander Graf wrote:
> >> KVM has an ioctl to define which signal mask should be used while running
> >> inside VCPU_RUN. At least for big endian systems, this mask is different
> >> on 32-bit and 64-bit systems (though the size is identical).
> >>
> >> Add a compat wrapper that converts the mask to whatever the kernel accepts,
> >> allowing 32-bit kvm user space to set signal masks.
> >>
> >> This patch fixes qemu with --enable-io-thread on ppc64 hosts when running
> >> 32-bit user land.
> >>
> >
> > This is already in (175c60204146b644), I believe the same version.
>
> Oh? I rebased again against origin/master and it's not there. Which tree do you want to have this against?
>
> git://git.kernel.org/pub/scm/virt/kvm/kvm.git
>
Sorry, it's in 'next' of the same repo. Usually the window between
'next' and 'master' is short, but I haven't run autotest in a while so
'master' is a bit stale.
I'll update master later today.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-06-19 13:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 14:49 [PULL 00/15] PPC KVM patch queue 2011-06-15 Alexander Graf
2011-06-17 14:49 ` [PATCH 01/15] KVM: PPC: fix partial application of "exit timing in ticks" Alexander Graf
2011-06-17 14:49 ` [PATCH 02/15] KVM: PPC: Resolve real-mode handlers through function exports Alexander Graf
2011-06-17 14:49 ` [PATCH 03/15] KVM: Add compat ioctl for KVM_SET_SIGNAL_MASK Alexander Graf
2011-06-19 9:04 ` Avi Kivity
2011-06-19 12:53 ` Alexander Graf
2011-06-19 13:01 ` Avi Kivity [this message]
2011-06-17 14:49 ` [PATCH 04/15] powerpc/e500: Save SPEFCSR in flush_spe_to_thread() Alexander Graf
2011-06-17 14:49 ` [PATCH 05/15] powerpc/e500: SPE register saving: take arbitrary struct offset Alexander Graf
2011-06-17 14:49 ` [PATCH 06/15] KVM: PPC: booke: use shadow_msr Alexander Graf
2011-06-17 14:49 ` [PATCH 07/15] KVM: PPC: e500: Save/restore SPE state Alexander Graf
2011-06-17 14:49 ` [PATCH 08/15] KVM: PPC: e500: Disable preloading TLB1 in tlb_load() Alexander Graf
2011-06-17 14:49 ` [PATCH 09/15] KVM: PPC: e500: don't use MAS0 as intermediate storage Alexander Graf
2011-06-17 14:49 ` [PATCH 10/15] KVM: PPC: e500: Eliminate shadow_pages[], and use pfns instead Alexander Graf
2011-06-17 14:49 ` [PATCH 11/15] KVM: PPC: e500: Support large page mappings of PFNMAP vmas Alexander Graf
2011-06-17 14:49 ` [PATCH 12/15] KVM: PPC: e500: enable magic page Alexander Graf
2011-06-17 14:49 ` [PATCH 13/15] KVM: PPC: e500: Stop keeping shadow TLB Alexander Graf
2011-06-17 14:49 ` [PATCH 14/15] KVM: PPC: e500: Add shadow PID support Alexander Graf
2011-06-17 14:49 ` [PATCH 15/15] KVM: PPC: e500: Don't search over the entire TLB0 Alexander Graf
2011-06-19 9:11 ` [PULL 00/15] PPC KVM patch queue 2011-06-15 Avi Kivity
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=4DFDF322.4060805@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.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