public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Andrew Jones <ajones@ventanamicro.com>
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: Wed, 22 Mar 2023 19:40:14 +0000	[thread overview]
Message-ID: <6d263b50-e2f0-4331-b930-c54e27f52fcc@spud> (raw)
In-Reply-To: <20230322192858.1189272-1-ajones@ventanamicro.com>


[-- Attachment #1.1: Type: text/plain, Size: 585 bytes --]

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>

Thanks,
Conor.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

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

  parent reply	other threads:[~2023-03-22 19:40 UTC|newest]

Thread overview: 11+ 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 ` [PATCH 1/2] RISC-V: KVM: Alphabetize selects Andrew Jones
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:40 ` Conor Dooley [this message]
2023-03-23 17:57   ` [PATCH 0/2] " Conor Dooley
2023-03-23 19:05     ` Andrew Jones
2023-03-24 11:32     ` Andrew Jones
2023-03-24 11:52       ` Conor Dooley
2023-03-24 11:56         ` Andrew Jones
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=6d263b50-e2f0-4331-b930-c54e27f52fcc@spud \
    --to=conor@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=atishp@atishpatra.org \
    --cc=kvm-riscv@lists.infradead.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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