All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: kvm@vger.kernel.org, andre.przywara@arm.com,
	sami.mujawar@arm.com, will@kernel.org,
	kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] kvmtool: arm64: Report missing support for 32bit guests
Date: Thu, 02 Jul 2020 16:51:24 +0100	[thread overview]
Message-ID: <31468a9ac80f34f1cb267c453dc914bb@kernel.org> (raw)
In-Reply-To: <0657181e-dff8-5bcc-add6-1b41df2993af@arm.com>

On 2020-07-02 16:37, Suzuki K Poulose wrote:
> Hi Marc
> 
> On 07/01/2020 04:42 PM, Marc Zyngier wrote:
>> On 2020-07-01 15:20, Suzuki K Poulose wrote:
>>> When the host doesn't support 32bit guests, the kvmtool fails
>>> without a proper message on what is wrong. i.e,
>>> 
>>>  $ lkvm run -c 1 Image --aarch32
>>>   # lkvm run -k Image -m 256 -c 1 --name guest-105618
>>>   Fatal: Unable to initialise vcpu
>>> 
>>> Given that there is no other easy way to check if the host supports 
>>> 32bit
>>> guests, it is always good to report this by checking the capability, 
>>> rather
>>> than leaving the users to hunt this down by looking at the code!
>>> 
>>> After this patch:
>>> 
>>>  $ lkvm run -c 1 Image --aarch32
>>>   # lkvm run -k Image -m 256 -c 1 --name guest-105695
>>>   Fatal: 32bit guests are not supported
>> 
>> Fancy!
>> 
>>> 
>>> Cc: Will Deacon <will@kernel.org>
>>> Reported-by: Sami Mujawar <sami.mujawar@arm.com>
>>> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
>>> ---
>>>  arm/kvm-cpu.c | 4 ++++
>>>  1 file changed, 4 insertions(+)
>>> 
>>> diff --git a/arm/kvm-cpu.c b/arm/kvm-cpu.c
>>> index 554414f..2acecae 100644
>>> --- a/arm/kvm-cpu.c
>>> +++ b/arm/kvm-cpu.c
>>> @@ -46,6 +46,10 @@ struct kvm_cpu *kvm_cpu__arch_init(struct kvm 
>>> *kvm,
>>> unsigned long cpu_id)
>>>          .features = ARM_VCPU_FEATURE_FLAGS(kvm, cpu_id)
>>>      };
>>> 
>>> +    if (kvm->cfg.arch.aarch32_guest &&
>>> +        !kvm__supports_extension(kvm, KVM_CAP_ARM_EL1_32BIT))
>> 
>> Can you please check that this still compiles for 32bit host?
> 
> Yes, it does. I have built this on an arm32 rootfs with make ARCH=arm.
> The kvm->cfg.arch is common across arm/arm64 and is defined here :
> 
> arm/include/arm-common/kvm-config-arch.h

I was worried about the availability of KVM_CAP_ARM_EL1_32BIT,
but being a capability, it is common to all arches. It is
KVM_ARM_VCPU_EL1_32BIT that is 32bit only, but that's not what
you are using. Too many flags! ;-)

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny...
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: kvm@vger.kernel.org, andre.przywara@arm.com,
	sami.mujawar@arm.com, will@kernel.org,
	kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] kvmtool: arm64: Report missing support for 32bit guests
Date: Thu, 02 Jul 2020 16:51:24 +0100	[thread overview]
Message-ID: <31468a9ac80f34f1cb267c453dc914bb@kernel.org> (raw)
In-Reply-To: <0657181e-dff8-5bcc-add6-1b41df2993af@arm.com>

On 2020-07-02 16:37, Suzuki K Poulose wrote:
> Hi Marc
> 
> On 07/01/2020 04:42 PM, Marc Zyngier wrote:
>> On 2020-07-01 15:20, Suzuki K Poulose wrote:
>>> When the host doesn't support 32bit guests, the kvmtool fails
>>> without a proper message on what is wrong. i.e,
>>> 
>>>  $ lkvm run -c 1 Image --aarch32
>>>   # lkvm run -k Image -m 256 -c 1 --name guest-105618
>>>   Fatal: Unable to initialise vcpu
>>> 
>>> Given that there is no other easy way to check if the host supports 
>>> 32bit
>>> guests, it is always good to report this by checking the capability, 
>>> rather
>>> than leaving the users to hunt this down by looking at the code!
>>> 
>>> After this patch:
>>> 
>>>  $ lkvm run -c 1 Image --aarch32
>>>   # lkvm run -k Image -m 256 -c 1 --name guest-105695
>>>   Fatal: 32bit guests are not supported
>> 
>> Fancy!
>> 
>>> 
>>> Cc: Will Deacon <will@kernel.org>
>>> Reported-by: Sami Mujawar <sami.mujawar@arm.com>
>>> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
>>> ---
>>>  arm/kvm-cpu.c | 4 ++++
>>>  1 file changed, 4 insertions(+)
>>> 
>>> diff --git a/arm/kvm-cpu.c b/arm/kvm-cpu.c
>>> index 554414f..2acecae 100644
>>> --- a/arm/kvm-cpu.c
>>> +++ b/arm/kvm-cpu.c
>>> @@ -46,6 +46,10 @@ struct kvm_cpu *kvm_cpu__arch_init(struct kvm 
>>> *kvm,
>>> unsigned long cpu_id)
>>>          .features = ARM_VCPU_FEATURE_FLAGS(kvm, cpu_id)
>>>      };
>>> 
>>> +    if (kvm->cfg.arch.aarch32_guest &&
>>> +        !kvm__supports_extension(kvm, KVM_CAP_ARM_EL1_32BIT))
>> 
>> Can you please check that this still compiles for 32bit host?
> 
> Yes, it does. I have built this on an arm32 rootfs with make ARCH=arm.
> The kvm->cfg.arch is common across arm/arm64 and is defined here :
> 
> arm/include/arm-common/kvm-config-arch.h

I was worried about the availability of KVM_CAP_ARM_EL1_32BIT,
but being a capability, it is common to all arches. It is
KVM_ARM_VCPU_EL1_32BIT that is 32bit only, but that's not what
you are using. Too many flags! ;-)

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny...

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: kvm@vger.kernel.org, andre.przywara@arm.com,
	sami.mujawar@arm.com, will@kernel.org,
	kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] kvmtool: arm64: Report missing support for 32bit guests
Date: Thu, 02 Jul 2020 16:51:24 +0100	[thread overview]
Message-ID: <31468a9ac80f34f1cb267c453dc914bb@kernel.org> (raw)
In-Reply-To: <0657181e-dff8-5bcc-add6-1b41df2993af@arm.com>

On 2020-07-02 16:37, Suzuki K Poulose wrote:
> Hi Marc
> 
> On 07/01/2020 04:42 PM, Marc Zyngier wrote:
>> On 2020-07-01 15:20, Suzuki K Poulose wrote:
>>> When the host doesn't support 32bit guests, the kvmtool fails
>>> without a proper message on what is wrong. i.e,
>>> 
>>>  $ lkvm run -c 1 Image --aarch32
>>>   # lkvm run -k Image -m 256 -c 1 --name guest-105618
>>>   Fatal: Unable to initialise vcpu
>>> 
>>> Given that there is no other easy way to check if the host supports 
>>> 32bit
>>> guests, it is always good to report this by checking the capability, 
>>> rather
>>> than leaving the users to hunt this down by looking at the code!
>>> 
>>> After this patch:
>>> 
>>>  $ lkvm run -c 1 Image --aarch32
>>>   # lkvm run -k Image -m 256 -c 1 --name guest-105695
>>>   Fatal: 32bit guests are not supported
>> 
>> Fancy!
>> 
>>> 
>>> Cc: Will Deacon <will@kernel.org>
>>> Reported-by: Sami Mujawar <sami.mujawar@arm.com>
>>> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
>>> ---
>>>  arm/kvm-cpu.c | 4 ++++
>>>  1 file changed, 4 insertions(+)
>>> 
>>> diff --git a/arm/kvm-cpu.c b/arm/kvm-cpu.c
>>> index 554414f..2acecae 100644
>>> --- a/arm/kvm-cpu.c
>>> +++ b/arm/kvm-cpu.c
>>> @@ -46,6 +46,10 @@ struct kvm_cpu *kvm_cpu__arch_init(struct kvm 
>>> *kvm,
>>> unsigned long cpu_id)
>>>          .features = ARM_VCPU_FEATURE_FLAGS(kvm, cpu_id)
>>>      };
>>> 
>>> +    if (kvm->cfg.arch.aarch32_guest &&
>>> +        !kvm__supports_extension(kvm, KVM_CAP_ARM_EL1_32BIT))
>> 
>> Can you please check that this still compiles for 32bit host?
> 
> Yes, it does. I have built this on an arm32 rootfs with make ARCH=arm.
> The kvm->cfg.arch is common across arm/arm64 and is defined here :
> 
> arm/include/arm-common/kvm-config-arch.h

I was worried about the availability of KVM_CAP_ARM_EL1_32BIT,
but being a capability, it is common to all arches. It is
KVM_ARM_VCPU_EL1_32BIT that is 32bit only, but that's not what
you are using. Too many flags! ;-)

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2020-07-02 15:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-01 14:20 [PATCH] kvmtool: arm64: Report missing support for 32bit guests Suzuki K Poulose
2020-07-01 14:20 ` Suzuki K Poulose
2020-07-01 14:20 ` Suzuki K Poulose
2020-07-01 15:42 ` Marc Zyngier
2020-07-01 15:42   ` Marc Zyngier
2020-07-01 15:42   ` Marc Zyngier
2020-07-02 15:37   ` Suzuki K Poulose
2020-07-02 15:37     ` Suzuki K Poulose
2020-07-02 15:37     ` Suzuki K Poulose
2020-07-02 15:51     ` Marc Zyngier [this message]
2020-07-02 15:51       ` Marc Zyngier
2020-07-02 15:51       ` Marc Zyngier
2020-07-03 12:07 ` Will Deacon
2020-07-03 12:07   ` Will Deacon
2020-07-03 12:07   ` Will Deacon

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=31468a9ac80f34f1cb267c453dc914bb@kernel.org \
    --to=maz@kernel.org \
    --cc=andre.przywara@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=sami.mujawar@arm.com \
    --cc=suzuki.poulose@arm.com \
    --cc=will@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 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.