All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Baptiste Reynal" <b.reynal@virtualopensystems.com>,
	"Thomas Huth" <thuth@redhat.com>,
	eric.auger@st.com, "Eric Auger" <eric.auger@linaro.org>,
	"Patch Tracking" <patches@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Peter Crosthwaite" <crosthwaitepeter@gmail.com>,
	qemu-arm <qemu-arm@nongnu.org>,
	"Suravee Suthikulpanit" <suravee.suthikulpanit@amd.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	thomas.lendacky@amd.com, "Alex Bennée" <alex.bennee@linaro.org>,
	"Christoffer Dall" <christoffer.dall@linaro.org>,
	"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH v6 0/8] AMD XGBE KVM platform passthrough
Date: Wed, 17 Feb 2016 12:59:39 -0700	[thread overview]
Message-ID: <20160217125939.6df646dc@t450s.home> (raw)
In-Reply-To: <CAFEAcA9UM_XQsd9nnZMnP3nxPwjf6PvW5KB5GdeJK+a29T0f2A@mail.gmail.com>

On Tue, 16 Feb 2016 18:40:47 +0000
Peter Maydell <peter.maydell@linaro.org> wrote:

> On 1 February 2016 at 13:51, Eric Auger <eric.auger@linaro.org> wrote:
> > This series allows to set up AMD XGBE passthrough. This was tested on AMD
> > Seattle.
> >
> > The first upstreamed device supporting KVM platform passthrough was the
> > Calxeda Midway XGMAC. Compared to this latter, the XGBE XGMAC exposes a
> > much more complex device tree node.
> >
> > - First There are 2 device tree node formats:
> > one where XGBE and PHY are described in separate nodes and another one
> > that combines both description in a single node (only supported by 4.2
> > onwards kernels). Only the combined description is supported for passthrough,
> > meaning the host must be >= 4.2 and must feature a device tree with a combined
> > description. The guest will also be exposed with a combined description,
> > meaning only >= 4.2 guest are supported. It is not planned to support
> > separate node representation since assignment of the PHY is less
> > straigtforward.
> >
> > - the XGMAC/PHY node depends on 2 clock nodes (DMA and PTP).
> > The code checks those clocks are fixed to make sure they cannot be
> > switched off at some point after the native driver gets unbound.
> >
> > - there are many property values to populate on guest side. Most of them
> > cannot be hardcoded. That series implements host device tree blob extraction
> > from the host /proc/device-tree (inspired from dtc implementation)
> > and retrieve host property values to populate guest dtb.
> >
> > - the case where the host uses ACPI is not yet covered since there is
> >   no usable ACPI description for this HW yet.
> >
> > The patches can be found at
> > https://git.linaro.org/people/eric.auger/qemu.git/shortlog/refs/heads/v2.5.0-xgbe-v6
> >
> > Previous versions can be found at
> > https://git.linaro.org/people/eric.auger/qemu.git/shortlog/refs/heads/v2.5.0-xgbe-v<n>  
> 
> I think you have review on everything in this series now, but I'm assuming
> this is going to go via the vfio tree (or at any rate not via target-arm).
> Let me know if that's wrong.

The little bit of vfio here looks ok to me too.  Eric, this doesn't
apply cleanly, could you please rebase and incorporate all the acks and
reviews and I'll send a pull request with it?  Thanks,

Alex

  reply	other threads:[~2016-02-17 19:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 13:51 [Qemu-devel] [PATCH v6 0/8] AMD XGBE KVM platform passthrough Eric Auger
2016-02-01 13:51 ` [Qemu-devel] [PATCH v6 1/8] hw/vfio/platform: amd-xgbe device Eric Auger
2016-02-01 13:51 ` [Qemu-devel] [PATCH v6 2/8] device_tree: introduce load_device_tree_from_sysfs Eric Auger
2016-02-01 16:15   ` Rob Herring
2016-02-01 16:22     ` Eric Auger
2016-02-01 16:27       ` Rob Herring
2016-02-01 16:31         ` Eric Auger
2016-02-16 18:37   ` Peter Maydell
2016-02-01 13:51 ` [Qemu-devel] [PATCH v6 3/8] device_tree: introduce qemu_fdt_node_path Eric Auger
2016-02-16 18:38   ` Peter Maydell
2016-02-01 13:51 ` [Qemu-devel] [PATCH v6 4/8] device_tree: qemu_fdt_getprop converted to use the error API Eric Auger
2016-02-01 13:51 ` [Qemu-devel] [PATCH v6 5/8] device_tree: qemu_fdt_getprop_cell " Eric Auger
2016-02-01 13:51 ` [Qemu-devel] [PATCH v6 6/8] hw/arm/sysbus-fdt: helpers for clock node generation Eric Auger
2016-02-01 13:51 ` [Qemu-devel] [PATCH v6 7/8] hw/arm/sysbus-fdt: enable amd-xgbe dynamic instantiation Eric Auger
2016-02-16 18:34   ` Peter Maydell
2016-02-01 13:51 ` [Qemu-devel] [PATCH v6 8/8] hw/arm/sysbus-fdt: remove qemu_fdt_setprop returned value check Eric Auger
2016-02-16 18:40   ` Peter Maydell
2016-02-16 18:40 ` [Qemu-devel] [PATCH v6 0/8] AMD XGBE KVM platform passthrough Peter Maydell
2016-02-17 19:59   ` Alex Williamson [this message]
2016-02-18 17:59     ` Eric Auger

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=20160217125939.6df646dc@t450s.home \
    --to=alex.williamson@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=b.reynal@virtualopensystems.com \
    --cc=christoffer.dall@linaro.org \
    --cc=crosthwaitepeter@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=eric.auger@linaro.org \
    --cc=eric.auger@st.com \
    --cc=patches@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=thomas.lendacky@amd.com \
    --cc=thuth@redhat.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 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.