qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
Cc: aliguori@us.ibm.com, "Alexander Graf" <agraf@suse.de>,
	zhlcindy@linux.vnet.ibm.com, qemu-devel@nongnu.org,
	"Li Zhang" <zhlcindy@gmail.com>, qemu-ppc <qemu-ppc@nongnu.org>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH 1/1] Add usb option in machine options.
Date: Fri, 15 Jun 2012 16:00:35 +1000	[thread overview]
Message-ID: <1339740035.9220.181.camel@pasglop> (raw)
In-Reply-To: <CAEgOgz49mPUpWEoyzLmDjusDu4cKftxL34XB4-dTm5JSTcun_Q@mail.gmail.com>

On Fri, 2012-06-15 at 15:15 +1000, Peter Crosthwaite wrote:
> 
> What should really happen here, is if you do change over to a machine
> opt, then all clients of the -usb should use the machine opt
> infrastructure, then the need for global state is eliminated
> completely.
> 
> But does this new -usb cmd line option have any connection to the
> existing -usb in this series? It looks like your trying to implement a
> new option to add/remove your usb controller, in which case, I think
> the best option is to do it using either configs or -device arguments.

The purpose is to have options for the ppc machines such as pseries to
disable the default usb controller.

IE. Those machines (well some of them at least) have no other input
device (no PS/2, no ADB, ...) and so in order to provide a semi-decent
user interface, we want to create an OHCI with mouse & keyboard
emulation along with the vga display by default, and have options to
disable those defaults for cases like libvirt where it really wants to
create all that stuff itself so it gets the right names.

VGA is already handled by a generic "high level" option (by opposition
to using -device which I qualify of "low level") -vga which takes an
argument and that argument can be "none". However, the generic "high
level"  -usb option doesn't take an argument and is only meant to
enable, not disable (and thus cannot be augmented easily without
breaking things).

So after the discussion on the list, we decided that -machine options is
the right way to handle that. I haven't had a chance to review Li's
patch itself and whether it does that though. Just chiming in on what
the intention is.

Cheers,
Ben.

  reply	other threads:[~2012-06-15  6:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14  5:17 [Qemu-devel] [PATCH 1/1] Add usb option in machine options zhlcindy
2012-06-14 14:27 ` Andreas Färber
2012-06-14 22:04   ` Benjamin Herrenschmidt
2012-06-15  2:34     ` Li Zhang
2012-06-15  3:06   ` Li Zhang
2012-06-15  5:15     ` Peter Crosthwaite
2012-06-15  6:00       ` Benjamin Herrenschmidt [this message]
2012-06-15  6:21       ` Li Zhang
2012-06-15 11:09     ` Andreas Färber
2012-06-15 12:46       ` Li 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=1339740035.9220.181.camel@pasglop \
    --to=benh@au1.ibm.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=peter.crosthwaite@petalogix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=zhlcindy@gmail.com \
    --cc=zhlcindy@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).