All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <ajones@ventanamicro.com>
To: kvm-riscv@lists.infradead.org
Subject: [PATCH 0/2] RISC-V: KVM: Require alternatives
Date: Thu, 23 Mar 2023 20:05:42 +0100	[thread overview]
Message-ID: <20230323190542.cubyq5p7tm2lzzd3@orel> (raw)
In-Reply-To: <427628e0-4c6d-4934-b873-fa1b81b7daa0@spud>

On Thu, Mar 23, 2023 at 05:57:14PM +0000, Conor Dooley wrote:
> On Wed, Mar 22, 2023 at 07:40:14PM +0000, Conor Dooley wrote:
> > On Wed, Mar 22, 2023 at 08:28:56PM +0100, Andrew Jones wrote:
> > > KVM makes use of riscv_has_extension_unlikely() to check for the
> > > svinval extension. riscv_has_extension_unlikely() is built on
> > > alternatives, which means KVM should ensure alternatives support
> > > is available.
> > > 
> > > The first patch takes the opportunity to cleanup KVM's select
> > > list. The second patch selects RISCV_ALTERNATIVE.
> > 
> > Reminds me, I need to re-submit my patch doing that for the top-level
> > RISC-V Kconfig...
> > For the pair:
> > Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
> 
> Actually, I would like to take this back for patch 2.
> Per the discussion on the other thread about XIP [1], I don't think
> that KVM should be selecting alternatives like this.
> Would you mind if I picked up these patches & submitted them as a v2,
> alongside a patch trying to make sure that we do not clip the wings of
> of XIP kernels by selecting RISCV_ALTERNATIVE?
> 

Sounds good to me. Thanks, Conor.

drew


WARNING: multiple messages have this Message-ID (diff)
From: Andrew Jones <ajones@ventanamicro.com>
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, kvm-riscv@lists.infradead.org,
	'Palmer Dabbelt ' <palmer@dabbelt.com>,
	'Anup Patel ' <anup@brainfault.org>,
	'Paul Walmsley ' <paul.walmsley@sifive.com>,
	'Atish Patra ' <atishp@atishpatra.org>,
	'Albert Ou ' <aou@eecs.berkeley.edu>
Subject: Re: [PATCH 0/2] RISC-V: KVM: Require alternatives
Date: Thu, 23 Mar 2023 20:05:42 +0100	[thread overview]
Message-ID: <20230323190542.cubyq5p7tm2lzzd3@orel> (raw)
In-Reply-To: <427628e0-4c6d-4934-b873-fa1b81b7daa0@spud>

On Thu, Mar 23, 2023 at 05:57:14PM +0000, Conor Dooley wrote:
> On Wed, Mar 22, 2023 at 07:40:14PM +0000, Conor Dooley wrote:
> > On Wed, Mar 22, 2023 at 08:28:56PM +0100, Andrew Jones wrote:
> > > KVM makes use of riscv_has_extension_unlikely() to check for the
> > > svinval extension. riscv_has_extension_unlikely() is built on
> > > alternatives, which means KVM should ensure alternatives support
> > > is available.
> > > 
> > > The first patch takes the opportunity to cleanup KVM's select
> > > list. The second patch selects RISCV_ALTERNATIVE.
> > 
> > Reminds me, I need to re-submit my patch doing that for the top-level
> > RISC-V Kconfig...
> > For the pair:
> > Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
> 
> Actually, I would like to take this back for patch 2.
> Per the discussion on the other thread about XIP [1], I don't think
> that KVM should be selecting alternatives like this.
> Would you mind if I picked up these patches & submitted them as a v2,
> alongside a patch trying to make sure that we do not clip the wings of
> of XIP kernels by selecting RISCV_ALTERNATIVE?
> 

Sounds good to me. Thanks, Conor.

drew

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

  reply	other threads:[~2023-03-23 19:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 19:28 [PATCH 0/2] RISC-V: KVM: Require alternatives Andrew Jones
2023-03-22 19:28 ` Andrew Jones
2023-03-22 19:28 ` [PATCH 1/2] RISC-V: KVM: Alphabetize selects Andrew Jones
2023-03-22 19:28   ` Andrew Jones
2023-04-07 11:47   ` Anup Patel
2023-04-07 11:47     ` Anup Patel
2023-03-22 19:28 ` [PATCH 2/2] RISC-V: KVM: Require alternatives Andrew Jones
2023-03-22 19:28   ` Andrew Jones
2023-03-22 19:40 ` [PATCH 0/2] " Conor Dooley
2023-03-22 19:40   ` Conor Dooley
2023-03-23 17:57   ` Conor Dooley
2023-03-23 17:57     ` Conor Dooley
2023-03-23 19:05     ` Andrew Jones [this message]
2023-03-23 19:05       ` Andrew Jones
2023-03-24 11:32     ` Andrew Jones
2023-03-24 11:32       ` Andrew Jones
2023-03-24 11:52       ` Conor Dooley
2023-03-24 11:52         ` Conor Dooley
2023-03-24 11:56         ` Andrew Jones
2023-03-24 11:56           ` Andrew Jones
2023-03-24 12:21           ` Anup Patel
2023-03-24 12:21             ` Anup Patel

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=20230323190542.cubyq5p7tm2lzzd3@orel \
    --to=ajones@ventanamicro.com \
    --cc=kvm-riscv@lists.infradead.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.