All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: "Gerd Hoffmann" <kraxel@redhat.com>,
	"Hongbo Zhang" <hongbo.zhang@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Radoslaw Biernacki" <radoslaw.biernacki@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	qemu-arm <qemu-arm@nongnu.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v4] hw/arm: Add arm SBSA reference machine
Date: Mon, 19 Nov 2018 09:17:34 -0800	[thread overview]
Message-ID: <CAKv+Gu9VjERXDdb=ZkvzVocL4Fd3_2e+F=H0nqEJVs4UEkYmhw@mail.gmail.com> (raw)
In-Reply-To: <20181119164421.me2j4fwzo43aghaa@bivouac.eciton.net>

On Mon, 19 Nov 2018 at 08:44, Leif Lindholm <leif.lindholm@linaro.org> wrote:
>
> On Mon, Nov 19, 2018 at 07:51:29AM -0800, Ard Biesheuvel wrote:
> > > > > I think what we *really* want is sysbus-xhci-generic.
> > > > >
> > > > > That'll be a bit more work though as xhci core and xhci pci needs to be
> > > > > splitted, simliar to how it was done for ehci in commit
> > > > > 5010d4dc618b6b8e7c21129c487c06f6493f71fc (and related patches).
> > > > >
> > > > > Or just plug qemu-xhci into a pcie slot.  Not sure which would be closer
> > > > > to physical hardware.
> > > >
> > > > We don't need XHCI especially, EHCI is perfectly fine as well.
> > > >
> > > > This is mostly about ensuring that the emulated hardware spans the
> > > > space of what we encounter on real hardware, and non-PCIE SATA and USB
> > > > controllers is something we see often.
> > > >
> > > > So I could live with MMIO SATA and PCI USB as well, but I'd prefer it
> > > > if we could have both MMIO.
> > >
> > > I would actually strongly prefer non-MMIO.
> > >
> > > What "we see" is generally a result of embedded companies "value
> > > adding" in the usual way when moving from embedded to servers.
> > >
> > > I want the SBSA target to be an idealised machine, not an educational
> > > vehicle for showing how companies have got it wrong.
> > >
> > > Where in doubt, anything software discoverable should win over
> > > non-discoverable.
> >
> > I don't think it makes sense at all to idealize the SBSA machine in
> > this way. For example, there are elaborate provisions in the IORT spec
> > how to describe an I/O topology involving named components (as opposed
> > to PCIe devices), and I have not seen an arm64 SoC yet that uses PCIe
> > internally for on-chip network controllers, nor do I expect to in the
> > near future. So having non-PCIe USB or SATA will permit us to exercise
> > code paths in the OS that we do rely on in production, and will for
> > the foreseeable future.
>
> Fair point.
>
> I have no objections at all to adding _some_ MMIO components for the
> purpose of being able to validate this. But I am reluctant to mandate
> discrepancies in bits that 99% of users would expect to work
> identically as it has done on x86.
>
> If USB isn't auto-instantiated in qemu-system-x86_64, then indeed we
> don't need to do it here either.
>
> But I assume you specifically want things that do a lot of DMA, so I
> couldn't get away with asking for keeping it to the SBSA UART(s)? :)
>

Ideally, it would be something that supports platform MSIs as well,
but that is unlikely to be a priority for anyone (and i would be very
surprised if any of QEMU's sysbus host controllers implement that at
the moment)

I can live with just sysbus AHCI, though, if EHCI/XHCI are too cumbersome.

  reply	other threads:[~2018-11-19 17:17 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-19  8:55 [Qemu-devel] [PATCH v4] Add arm SBSA reference machine Hongbo Zhang
2018-10-19  8:55 ` [Qemu-devel] [PATCH v4] hw/arm: " Hongbo Zhang
2018-11-15 16:05   ` Peter Maydell
2018-11-16 10:46     ` Hongbo Zhang
2018-11-16 11:29       ` Peter Maydell
2018-11-19 10:49         ` Hongbo Zhang
2018-11-19 10:54           ` Hongbo Zhang
2018-12-06  9:19         ` Hongbo Zhang
2018-11-16 12:27       ` Gerd Hoffmann
2018-11-16 22:04         ` Ard Biesheuvel
2018-11-19 12:44           ` Leif Lindholm
2018-11-19 15:51             ` Ard Biesheuvel
2018-11-19 16:44               ` Leif Lindholm
2018-11-19 17:17                 ` Ard Biesheuvel [this message]
2018-11-20  8:16                   ` Gerd Hoffmann
2018-11-20  8:49                     ` Hongbo Zhang
2018-11-20  9:40                       ` Ard Biesheuvel
2018-11-21  8:35                         ` Hongbo Zhang
2018-12-29  9:52                           ` Hongbo Zhang
2018-11-23  7:14     ` Hongbo Zhang
2018-11-23  7:32       ` Hongbo Zhang
2018-12-05  9:50     ` Hongbo Zhang
2018-12-05 10:36       ` Leif Lindholm
2018-12-06  1:50         ` Hongbo Zhang
2019-01-29 11:28     ` Ard Biesheuvel
2019-01-30  8:34       ` Hongbo Zhang
2019-01-30  8:37         ` Ard Biesheuvel
2019-01-31 13:21           ` Radoslaw Biernacki
2018-11-05 16:31 ` [Qemu-devel] [PATCH v4] " Peter Maydell
2018-11-06 10:16   ` Hongbo Zhang
2018-11-15 16:20 ` Peter Maydell
2018-11-15 18:59   ` Ard Biesheuvel
2018-11-16  8:23   ` Hongbo Zhang
2018-11-16  9:58     ` Peter Maydell
2018-11-16 10:52       ` Hongbo Zhang

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='CAKv+Gu9VjERXDdb=ZkvzVocL4Fd3_2e+F=H0nqEJVs4UEkYmhw@mail.gmail.com' \
    --to=ard.biesheuvel@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=hongbo.zhang@linaro.org \
    --cc=kraxel@redhat.com \
    --cc=leif.lindholm@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=radoslaw.biernacki@linaro.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.