All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair Francis <alistair.francis@xilinx.com>
To: Alexander Graf <agraf@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	Kim Phillips <kim.phillips@freescale.com>,
	eric.auger@st.com, Eric Auger <eric.auger@linaro.org>,
	Kim Phillips <kim.phillips@linaro.org>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	Alistair Francis <alistair.francis@xilinx.com>,
	stuart.yoder@freescale.com, alex.williamson@redhat.com,
	christophe.barnichon@st.com, a.motakis@virtualopensystems.com,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [Qemu-devel] [RFC v2 1/6] hw/arm/virt: add a xgmac device
Date: Fri, 11 Apr 2014 15:41:10 +1000	[thread overview]
Message-ID: <CAKmqyKPjzf8ga=KM1eFrVii8pZU_LqXhaJrqVKNdm-esAsXWGg@mail.gmail.com> (raw)
In-Reply-To: <5346A148.4040004@suse.de>

On Thu, Apr 10, 2014 at 11:48 PM, Alexander Graf <agraf@suse.de> wrote:
>
> On 10.04.14 15:26, Peter Crosthwaite wrote:
>>
>> On Thu, Apr 10, 2014 at 1:33 AM, Eric Auger <eric.auger@linaro.org> wrote:
>>>
>>> From: Kim Phillips <kim.phillips@linaro.org>
>>>
>>> This is a hack and only serves as an example of what needs to be
>>> done to make the next RFC - add vfio-platform support - work
>>> for development purposes on a Calxeda Midway system.  We don't want
>>> mach-virt to always create this ethernet device - DO NOT APPLY, etc.
>>>
>>> Initial attempts to convince QEMU to create a memory mapped device
>>> on the command line (e.g., -device vfio-platform,name=fff51000.ethernet)
>>> would fail with "Parameter 'driver' expects pluggable device type".
>>
>> Alistair is working on this. cc.
>
>
> Alaistair, I've had patches tackle this on the mailing list a few months ago
> and received good comments from Anthony on what to change. How far in are
> you already? I'd like to make sure we're on the same page here (and don't
> duplicate work).
>
>
> Alex
>
>

Hey Alex,

I have a patch I'm about to send to the mailing list. It allows an
entire machine to be added by the -device argument on the command
line. It is a similar implementation to my first version (vl.c: Allow
sysbus devices to be attached via commandline), but much more generic.

Could you point me to your patches so I can compare? At the moment I
don't have much feedback to my implementation

Thanks,

Alistair

  reply	other threads:[~2014-04-11  5:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09 15:33 [Qemu-devel] [RFC v2 0/6] KVM platform device passthrough Eric Auger
2014-04-09 15:33 ` [Qemu-devel] [RFC v2 1/6] hw/arm/virt: add a xgmac device Eric Auger
2014-04-10 13:26   ` Peter Crosthwaite
2014-04-10 13:48     ` Alexander Graf
2014-04-11  5:41       ` Alistair Francis [this message]
2014-04-11  9:21         ` Alexander Graf
2014-04-09 15:33 ` [Qemu-devel] [RFC v2 2/6] vfio: move hw/misc/vfio.c to hw/vfio/pci.c Eric Auger
2014-04-09 15:33 ` [Qemu-devel] [RFC v2 3/6] vfio: add vfio-platform support Eric Auger
     [not found]   ` <1397832861.3060.93.camel@ul30vt.home>
2014-05-20  6:44     ` Eric Auger
2014-04-09 15:33 ` [Qemu-devel] [RFC v2 4/6] vfio: Add initial IRQ support in QEMU platform device Eric Auger
2014-04-11  1:34   ` Kim Phillips
2014-04-09 15:33 ` [Qemu-devel] [RFC v2 5/6] virt: Assign a VFIO platform device to a virt VM in QEMU command line Eric Auger
2014-04-09 15:33 ` [Qemu-devel] [RFC v2 6/6] vfio: add exit function and IRQ disable functions Eric Auger
2014-04-11  1:28 ` [Qemu-devel] [RFC v2 0/6] KVM platform device passthrough Kim Phillips

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='CAKmqyKPjzf8ga=KM1eFrVii8pZU_LqXhaJrqVKNdm-esAsXWGg@mail.gmail.com' \
    --to=alistair.francis@xilinx.com \
    --cc=a.motakis@virtualopensystems.com \
    --cc=agraf@suse.de \
    --cc=alex.williamson@redhat.com \
    --cc=christoffer.dall@linaro.org \
    --cc=christophe.barnichon@st.com \
    --cc=eric.auger@linaro.org \
    --cc=eric.auger@st.com \
    --cc=kim.phillips@freescale.com \
    --cc=kim.phillips@linaro.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stuart.yoder@freescale.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.