qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Gerhard Wiesinger <lists@wiesinger.com>,
	qemu-devel@nongnu.org, Hannes Reinecke <hare@suse.de>,
	Andreas Faerber <afaerber@suse.de>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH][v14] megasas: LSI Megaraid SAS HBA emulation
Date: Fri, 24 Feb 2012 17:05:30 +0100	[thread overview]
Message-ID: <5EAF9E40-85DA-496C-B423-5AD51A97C242@suse.de> (raw)
In-Reply-To: <4F47B393.7070606@codemonkey.ws>


On 24.02.2012, at 16:58, Anthony Liguori wrote:

> On 02/23/2012 09:34 AM, Michael S. Tsirkin wrote:
>> On Tue, Feb 21, 2012 at 10:36:43AM +0100, Hannes Reinecke wrote:
>>> This patch adds an emulation for the LSI Megaraid SAS 8708EM2 HBA.
>>> I've tested it to work with Linux, Windows Vista, and Windows7.
>>> MSI-X support is currently broken; have to investigate.
>>> 
>>> Changes since v13:
>>> - Remove separate MSI-X BAR
>>> - Simplify BAR allocation
>>> 
>>> Changes since v12:
>>> - Fixup flag setting via properties
>>> - Fixup MSI-X handling
>>> - Disable MSI-X per default
>>> 
>>> Changes since v11:
>>> - Remove unneeded variables
>>> 
>>> Changes since v10:
>>> - Port to new device type API
>>> - Include suggestion from Alex Graf:
>>> - Remove 'inline' function declaration
>>> - Queue setup and interrupt enablement needs to be treated
>>>   independently
>>> - Always read in 64 bit context and just mask out the top
>>>   bits if required
>>> 
>>> Changes since v9:
>>> - Split off trace events into a separate patch
>>> - Do not check for max_luns in PD Info
>>> - Update trace events
>>> - Clarify license statement
>>> - Fixup coding style issues
>>> 
>>> Changes since v8:
>>> - Remove 'disable' keyword from trace definitions
>>> - Convert hand-crafted debugging statements with trace
>>>   definitions
>>> - Treat 'context' tag as little endian
>>> 
>>> Changes since v7:
>>> - Port to new memory API
>>> - Port to new PCI infrastructure
>>> - Use fixed buffers for sense processing
>>> - Update to updated SCSI infrastructure
>>> 
>>> Changes since v6:
>>> - Preliminary patches pushed to Kevins block tree
>>> - Implement 64bit contexts, required for Windows7
>>> - Use iovecs for DCMD processing
>>> - Add MSI-X support
>>>   Latest Linux driver now happily uses MSI-X.
>>> - Static iovec allocation
>>>   We have a fixed upper number of iovecs, so we can
>>>   save us the allocation. Suggested by Alex Graf.
>>> - Update MFI header
>>>   Latest Linux driver has some more definitions,
>>>   add them
>>> - Fixup AEN handling
>>> - Update tracing details
>>> - Remove sdev pointer from megasas_cmd_t
>>> 
>>> Changes since v5:
>>> - megasas: Use tracing infrastructure instead of DPRINTF
>>> - megasas: Use new PCI infrastructure
>>> - megasas: Check for iovec mapping failure
>>>   cpu_map_physical_memory() might fail, so we need to check for
>>>   it when mapping iovecs.
>>> - megasas: Trace scsi buffer overflow
>>>   The transfer length as specified in the SCSI command might
>>>   disagree with the length of the iovec. We should be tracing
>>>   these issues.
>>> - megasas: Reset frames after init firmware
>>>   When receiving an INIT FIRMWARE command we need reset all
>>>   frames, otherwise some frames might point to invalid memory.
>>> 
>>> Chances since v4:
>>> - megasas: checkpatch.pl fixes and update to work with the
>>>   changed interface in scsi_req_new(). Also included the
>>>   suggested fixes from Alex.
>>> 
>>> Signed-off-by: Hannes Reinecke<hare@suse.de>
>>> Cc: Alexander Graf<agraf@suse.de>
>>> Cc: Andreas Faerber<afaerber@suse.de>
>>> Cc: Gerhard Wiesinger<lists@wiesinger.com>
>> 
>> So Alex asked whether I can merge this, which made me
>> take a look. I don't know much about what this does
>> so just general comments on all of the code.
> 
> This should come through Paolo's new SCSI tree.
> 
> And while I defended this before, I now think it really ought to be split after trying (and failing) to trim the bits below in Thunderbird.

Split up in what pieces? The only natural split I could think of would be mfi.h and megasas.c. Splitting megasas.c inside of itself doesn't really make sense, as it's just a new device and useless when not complete.

Alex

  reply	other threads:[~2012-02-24 16:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-21  9:36 [Qemu-devel] [PATCH][v14] megasas: LSI Megaraid SAS HBA emulation Hannes Reinecke
2012-02-21 18:54 ` Gerhard Wiesinger
2012-02-23  7:03   ` Gerhard Wiesinger
2012-02-23  7:14     ` Andreas Färber
2012-02-23  7:20       ` Gerhard Wiesinger
2012-02-23  7:12 ` Alexander Graf
2012-02-23 15:34 ` Michael S. Tsirkin
2012-02-24 15:58   ` Anthony Liguori
2012-02-24 16:05     ` Alexander Graf [this message]
2012-02-24 16:13       ` Anthony Liguori
2012-02-27  9:17   ` Hannes Reinecke
2012-02-27 10:31     ` Michael S. Tsirkin
2012-02-27 15:24       ` Hannes Reinecke
2012-03-02  7:20         ` Gerhard Wiesinger
2012-02-27 13:47   ` Andreas Färber

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=5EAF9E40-85DA-496C-B423-5AD51A97C242@suse.de \
    --to=agraf@suse.de \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=hare@suse.de \
    --cc=lists@wiesinger.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.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 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).