From: "Raslan, KarimAllah" <karahmed@amazon.de>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>
Cc: "rkrcmar@redhat.com" <rkrcmar@redhat.com>
Subject: Re: [PATCH] KVM: Switch 'requests' to be 64-bit (explicitly)
Date: Tue, 22 May 2018 15:42:08 +0000 [thread overview]
Message-ID: <1527003728.13207.55.camel@amazon.de> (raw)
In-Reply-To: <53700469-74f0-f3b0-96a4-d8ace2919b36@redhat.com>
On Mon, 2018-04-16 at 18:28 +0200, Paolo Bonzini wrote:
> On 15/04/2018 00:26, KarimAllah Ahmed wrote:
> >
> > Switch 'requests' to be explicitly 64-bit and update BUILD_BUG_ON check to
> > use the size of "requests" instead of the hard-coded '32'.
> >
> > That gives us a bit more room again for arch-specific requests as we
> > already ran out of space for x86 due to the hard-coded check.
> >
> > Cc: Paolo Bonzini <pbonzini@redhat.com>
> > Cc: Radim Krčmář <rkrcmar@redhat.com>
> > Cc: kvm@vger.kernel.org
> > Cc: linux-kernel@vger.kernel.org
> > Signed-off-by: KarimAllah Ahmed <karahmed@amazon.de>
>
> I'm afraid architectures like ARM 32 need this to be conditional (using
> Kconfig).
Why would using a 64-bit 'requests' be a problem for ARM32? Are you
concerned about performance here or is there some symantic problem?
>
> Thanks,
>
> Paolo
>
> >
> > ---
> > include/linux/kvm_host.h | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
> > index 6930c63..fe4f46b 100644
> > --- a/include/linux/kvm_host.h
> > +++ b/include/linux/kvm_host.h
> > @@ -129,7 +129,7 @@ static inline bool is_error_page(struct page *page)
> > #define KVM_REQUEST_ARCH_BASE 8
> >
> > #define KVM_ARCH_REQ_FLAGS(nr, flags) ({ \
> > - BUILD_BUG_ON((unsigned)(nr) >= 32 - KVM_REQUEST_ARCH_BASE); \
> > + BUILD_BUG_ON((unsigned)(nr) >= (sizeof(((struct kvm_vcpu *)0)->requests) * 8) - KVM_REQUEST_ARCH_BASE); \
> > (unsigned)(((nr) + KVM_REQUEST_ARCH_BASE) | (flags)); \
> > })
> > #define KVM_ARCH_REQ(nr) KVM_ARCH_REQ_FLAGS(nr, 0)
> > @@ -223,7 +223,7 @@ struct kvm_vcpu {
> > int vcpu_id;
> > int srcu_idx;
> > int mode;
> > - unsigned long requests;
> > + u64 requests;
> > unsigned long guest_debug;
> >
> > int pre_pcpu;
> > @@ -1122,7 +1122,7 @@ static inline void kvm_make_request(int req, struct kvm_vcpu *vcpu)
> > * caller. Paired with the smp_mb__after_atomic in kvm_check_request.
> > */
> > smp_wmb();
> > - set_bit(req & KVM_REQUEST_MASK, &vcpu->requests);
> > + set_bit(req & KVM_REQUEST_MASK, (void *)&vcpu->requests);
> > }
> >
> > static inline bool kvm_request_pending(struct kvm_vcpu *vcpu)
> > @@ -1132,12 +1132,12 @@ static inline bool kvm_request_pending(struct kvm_vcpu *vcpu)
> >
> > static inline bool kvm_test_request(int req, struct kvm_vcpu *vcpu)
> > {
> > - return test_bit(req & KVM_REQUEST_MASK, &vcpu->requests);
> > + return test_bit(req & KVM_REQUEST_MASK, (void *)&vcpu->requests);
> > }
> >
> > static inline void kvm_clear_request(int req, struct kvm_vcpu *vcpu)
> > {
> > - clear_bit(req & KVM_REQUEST_MASK, &vcpu->requests);
> > + clear_bit(req & KVM_REQUEST_MASK, (void *)&vcpu->requests);
> > }
> >
> > static inline bool kvm_check_request(int req, struct kvm_vcpu *vcpu)
> >
>
>
Amazon Development Center Germany GmbH
Berlin - Dresden - Aachen
main office: Krausenstr. 38, 10117 Berlin
Geschaeftsfuehrer: Dr. Ralf Herbrich, Christian Schlaeger
Ust-ID: DE289237879
Eingetragen am Amtsgericht Charlottenburg HRB 149173 B
next prev parent reply other threads:[~2018-05-22 15:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-14 22:26 [PATCH] KVM: Switch 'requests' to be 64-bit (explicitly) KarimAllah Ahmed
2018-04-15 13:12 ` Raslan, KarimAllah
2018-04-16 16:26 ` Jim Mattson
2018-04-16 16:28 ` Paolo Bonzini
2018-05-22 15:42 ` Raslan, KarimAllah [this message]
2018-05-22 15:47 ` Paolo Bonzini
2018-07-05 12:22 ` Raslan, KarimAllah
2018-07-05 12:41 ` Paolo Bonzini
2018-07-05 13:51 ` Mark Rutland
2018-07-10 9:37 ` Raslan, KarimAllah
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=1527003728.13207.55.camel@amazon.de \
--to=karahmed@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.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.