public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "Leubner, Achim" <Achim_Leubner@adaptec.com>,
	Christoph Hellwig <hch@infradead.org>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] fix gcc warning on 64 bit compile of gdth
Date: Tue, 4 Jan 2005 10:29:41 +0000	[thread overview]
Message-ID: <20050104102941.GC26051@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1104831161.4215.17.camel@laptopd505.fenrus.org>

On Tue, Jan 04, 2005 at 10:32:41AM +0100, Arjan van de Ven wrote:
> On Tue, 2005-01-04 at 10:29 +0100, Leubner, Achim wrote:
> > You are right, in gdth_fill_raw_command() the driver is doing two
> > different dma mappings, one for the data buffer stored in
> > SCp.dma_handle, and the second for the sense buffer stored in SCp.buffer
> > and host_scribble. So reuse of dma_handle does not work here.
> 
> Is there a way the driver can get rid of looking at the sense buffer at
> all and let the midlayer do this ?

AFAICS, hardware wants dma_address of that puppy passed to it.  Which might
be a solution of this problem, if that address is not clobbered and can
be read back from where we'd stored it.  But that's a question for hardware
folks - does the value of cmdp->u.{raw,raw64}.sense_data survive until we
get to unmapping stuff in gdth_sync_event()?

In any case, we really should check for failure of pci_map_...() and be
more careful with checking if two areas need to be unmapped...

  reply	other threads:[~2005-01-04 10:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-04  9:29 [PATCH] fix gcc warning on 64 bit compile of gdth Leubner, Achim
2005-01-04  9:32 ` Arjan van de Ven
2005-01-04 10:29   ` Al Viro [this message]
2005-01-05 11:19   ` Christoph Hellwig
2005-01-04 14:55 ` James Bottomley
2005-01-05 11:19 ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2005-01-04 12:08 Leubner, Achim
2005-01-04 10:57 Leubner, Achim
2005-01-04 11:53 ` Al Viro
2005-01-03 21:45 James Bottomley
2005-01-03 22:43 ` Al Viro
2005-01-03 22:49   ` James Bottomley
2005-01-03 22:54     ` Al Viro
2005-01-03 23:53       ` James Bottomley
2005-01-04  4:52         ` Al Viro
2005-01-04  8:27       ` Christoph Hellwig

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=20050104102941.GC26051@parcelfarce.linux.theplanet.co.uk \
    --to=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=Achim_Leubner@adaptec.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=arjan@infradead.org \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.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