From: Paolo Bonzini <pbonzini@redhat.com>
To: "Raslan, KarimAllah" <karahmed@amazon.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Cc: "rkrcmar@redhat.com" <rkrcmar@redhat.com>
Subject: Re: [PATCH] KVM: Switch 'requests' to be 64-bit (explicitly)
Date: Tue, 22 May 2018 17:47:42 +0200 [thread overview]
Message-ID: <5f346c4e-73f2-6a73-7915-e9fa911191ec@redhat.com> (raw)
In-Reply-To: <1527003728.13207.55.camel@amazon.de>
On 22/05/2018 17:42, Raslan, KarimAllah wrote:
> 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?
They don't support atomics on double-word data.
Paolo
next prev parent reply other threads:[~2018-05-22 15:47 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
2018-05-22 15:47 ` Paolo Bonzini [this message]
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=5f346c4e-73f2-6a73-7915-e9fa911191ec@redhat.com \
--to=pbonzini@redhat.com \
--cc=karahmed@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox