All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: Alexander Graf <agraf@suse.de>
Cc: stefanha@gmail.com, kraxel@redhat.com, qemu-devel@nongnu.org,
	nab@linux-iscsi.org, Hannes Reinecke <hare@suse.de>
Subject: Re: [Qemu-devel] [PATCH] Make SCSI HBA configurable
Date: Thu, 25 Nov 2010 13:22:30 +0000	[thread overview]
Message-ID: <201011251322.31081.paul@codesourcery.com> (raw)
In-Reply-To: <A75C3595-D6D2-4CD7-853B-CBD2294E3131@suse.de>

> On 25.11.2010, at 11:59, Paul Brook wrote:
> >> This patch introduces configuration variables
> >> CONFIG_SCSI_LSI
> >> CONFIG_SCSI_MEGASAS
> >> and renames the existing CONFIG_ESP to CONFIG_SCSI_ESP.
> >> With this the available SCSI HBAs can be configured for each
> >> target configuration instead of compiling it in for everyone.
> > 
> > No. These are both PCI devices, I see no particularly good reason to make
> > them optional. At minimum they should be enabled by default on all
> > configs.
> > 
> > The ESP controller is different because it is't a general purpose device,
> > and only makes sense on certain systems.
> 
> RH needs to compile out as much as they can from the code base, because
> they state that they support everything that's compiled in. So making as
> much as possible optional is good. And I don't see why we should limit
> ourselves here.

My second point (should be enabled by default) still applies.  Your patch 
removes the lsi controller from the default arm-softmmu config, which is 
definitely wrong.

Paul

  reply	other threads:[~2010-11-25 13:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 10:15 [Qemu-devel] [PATCH] Make SCSI HBA configurable Hannes Reinecke
2010-11-22 11:04 ` [Qemu-devel] " Paolo Bonzini
2010-11-22 15:05 ` [Qemu-devel] " Jes Sorensen
2010-11-22 22:01   ` Alexander Graf
2010-11-25 10:59 ` Paul Brook
2010-11-25 12:54   ` Alexander Graf
2010-11-25 13:22     ` Paul Brook [this message]
2010-11-25 13:24       ` Alexander Graf
2010-11-26  8:01       ` Jes Sorensen

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=201011251322.31081.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=agraf@suse.de \
    --cc=hare@suse.de \
    --cc=kraxel@redhat.com \
    --cc=nab@linux-iscsi.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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.