From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: Alexandru Elisei <alexandru.elisei@arm.com>,
Rajnesh Kanwal <rkanwal@rivosinc.com>,
apatel@ventanamicro.com, atishp@rivosinc.com,
kvm@vger.kernel.org, julien.thierry.kdev@gmail.com,
andre.przywara@arm.com
Subject: Re: [PATCH kvmtool 1/1] riscv: pci: Add --force-pci option for riscv VMs.
Date: Sat, 21 Jan 2023 12:18:51 +0000 [thread overview]
Message-ID: <86ilh0m66s.wl-maz@kernel.org> (raw)
In-Reply-To: <20230119181615.GB20563@willie-the-truck>
On Thu, 19 Jan 2023 18:16:15 +0000,
Will Deacon <will@kernel.org> wrote:
>
> On Thu, Jan 19, 2023 at 01:39:32PM +0000, Alexandru Elisei wrote:
> > Hi,
> >
> > CC'ing the kvmtool maintainers and other people that might be interested in this
> > thread. Sorry for hijacking your patch!
> >
> > On Wed, Jan 18, 2023 at 05:20:07PM +0000, Rajnesh Kanwal wrote:
> > > Adding force-pci option to allow forcing virtio
> > > devices to use pci as the default transport.
> >
> > arm is in the same situation, MMIO is the default virtio transport. I was bitten
> > by that in the past. It also cought other people unaware, and I remember maz
> > complaining about it on the list.
> >
> > So I was thinking about adding a new command line parameter, --virtio-transport,
> > with the possible values mmio-legacy, mmio, pci-legacy and pci. Then each
> > architecture can define the default value for the transport. For arm, that would
> > be pci.
> >
> > What do you guys think?
>
> That sounds good to me. Then we can remove --force-pci altogether and maybe
> have PCI as the default for everybody? Should make the tool a little easier
> to use across architectures.
I'd rather keep --force-pci in order no to break existing scripting.
It just won't do anything once we make PCI the default (which we
definitely should).
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2023-01-21 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 17:20 [PATCH kvmtool 1/1] riscv: pci: Add --force-pci option for riscv VMs Rajnesh Kanwal
2023-01-19 13:39 ` Alexandru Elisei
2023-01-19 14:24 ` Andre Przywara
2023-01-19 18:16 ` Will Deacon
2023-01-21 12:18 ` Marc Zyngier [this message]
2023-01-21 15:41 ` Alexandru Elisei
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=86ilh0m66s.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=andre.przywara@arm.com \
--cc=apatel@ventanamicro.com \
--cc=atishp@rivosinc.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=rkanwal@rivosinc.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.