All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Kamada <kama@jp.fujitsu.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: kama@jp.fujitsu.com, xen-devel@lists.xensource.com
Subject: Re: [PATCH 0/5] pvSCSI (SCSI pass through) driver
Date: Thu, 25 Oct 2007 10:59:31 +0900	[thread overview]
Message-ID: <20071025105803.5A32.KAMA@jp.fujitsu.com> (raw)
In-Reply-To: <C344B5FE.F680%Keir.Fraser@cl.cam.ac.uk>

Keir-san,

On Wed, 24 Oct 2007 08:42:38 +0100
Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
> On 24/10/07 07:22, "Jun Kamada" <kama@jp.fujitsu.com> wrote:
> 
> >> Anyway, the right answer is to ensure that your structures compile the same
> >> whether compiled with 32-bit or 64-bit gcc. Check the structure sizes,
> >> fields sizes and field offsets.
> > 
> > You showed me two options in previous email; i.) all the shared-memory
> > structures defined in vscsiif.h compile identically for 32-bit and
> > 64-bit mode, ii.) to detect the frontend's 'bitness' in scsiback and
> > optionally do 32-to-64 or 64-to-32 conversion.
> > 
> > I consider that current VBD implementation takes option ii.), however
> > you recommended me to take option i.) for pvSCSI driver.
> > Is my understanding right?
> 
> Yes. It was an accident we ended up with structures compiling differently on
> 32- vs 64-bit. By the time we discovered it was an issue, we couldn't break
> backward compatibility.

I understood. I'll try to modify the pvSCSI driver by option i.).

Best regards,

-----
Jun Kamada

  reply	other threads:[~2007-10-25  1:59 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  5:15 [PATCH 0/5] pvSCSI (SCSI pass through) driver Jun Kamada
2007-10-19  8:38 ` Keir Fraser
2007-10-19 10:20   ` Ian Pratt
2007-10-22  2:39     ` Jun Kamada
2007-10-22  0:07 ` James Harper
2007-10-23  7:41   ` Jun Kamada
2007-10-22  8:58 ` Keir Fraser
2007-10-23  7:09   ` Jun Kamada
2007-10-23  8:50     ` Keir Fraser
2007-10-23 11:35       ` Jun Kamada
2007-10-23 12:39         ` Keir Fraser
2007-10-24  6:22           ` Jun Kamada
2007-10-24  7:42             ` Keir Fraser
2007-10-25  1:59               ` Jun Kamada [this message]
2007-10-30 10:39                 ` [PATCH 0/6] " Jun Kamada
2007-10-30 10:56                   ` Keir Fraser
2007-10-31  8:37                     ` Jun Kamada
2007-10-31  9:10                       ` Keir Fraser
2007-10-31 10:56                         ` Jun Kamada
2007-10-31 11:15                           ` Keir Fraser
2007-11-01 12:14                   ` Stephen C. Tweedie
2007-11-02  0:23                     ` James Harper
2007-11-05  3:30                       ` Jun Kamada
2007-11-05  2:05                     ` Jun Kamada
2007-11-08 21:33                       ` Stephen C. Tweedie
2007-11-12  8:27                         ` Jun Kamada
2007-11-05  3:34                     ` Aaron Dailey
2007-10-30 10:39                 ` [PATCH 1/6] " Jun Kamada
2007-10-30 10:39                 ` [PATCH 2/6] " Jun Kamada
2007-10-30 10:39                 ` [PATCH 3/6] " Jun Kamada
2007-10-30 10:39                 ` [PATCH 4/6] " Jun Kamada
2007-10-30 10:39                 ` [PATCH 5/6] " Jun Kamada
2007-10-30 10:39                 ` [PATCH 6/6] " Jun Kamada

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=20071025105803.5A32.KAMA@jp.fujitsu.com \
    --to=kama@jp.fujitsu.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.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.