All of lore.kernel.org
 help / color / mirror / Atom feed
From: konrad.wilk@oracle.com (Konrad Rzeszutek Wilk)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] xen/block: Correctly define structures in public headers on ARM32 and ARM64
Date: Tue, 3 Dec 2013 13:01:39 -0500	[thread overview]
Message-ID: <20131203180139.GG3734@phenom.dumpdata.com> (raw)
In-Reply-To: <529E109A.7050700@citrix.com>

On Tue, Dec 03, 2013 at 05:10:50PM +0000, David Vrabel wrote:
> On 03/12/13 15:40, Julien Grall wrote:
> > On ARM (32 bits and 64 bits), the double-word is 8-bytes aligned. This will
> > result on different structure from Xen and Linux repositories.
> > 
> > As Linux is using __packed__ attribute, it must have a 4-bytes padding before
> > each "id" field.
> > 
> > This change breaks guest block support with older kernel. IMHO, it's acceptable
> > because Xen on ARM is still on Tech Preview and the hypercall ABI is not yet
> > freezed.
> > 
> > Only one architecture (x86_32) doesn't have 64-bit ABI for the block interface.
> > Don't add padding if Linux is compiled for this architecture.
> 
> I'm now satisfied that this is the right thing to do.
> 
> Acked-by: David Vrabel <david.vrabel@citrix.com>

Before we go any further, I need testing confirmation that with this patch
can still run on x86 hardware the following combinations:

 32-bit guest on 64-bit dom0
 64-bit guest on 32-bit dom0

and with an 3.12 dom0

B/c I am not seeing that mentioned anywhere and I think that is creating
confusion with folks thinking it would break the x86-world (which it shouldn't).

> 
> David

WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Julien Grall <julien.grall@linaro.org>,
	xen-devel@lists.xenproject.org, patches@linaro.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Roger Pau Monne <roger.pau@citrix.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v2] xen/block: Correctly define structures in public headers on ARM32 and ARM64
Date: Tue, 3 Dec 2013 13:01:39 -0500	[thread overview]
Message-ID: <20131203180139.GG3734@phenom.dumpdata.com> (raw)
In-Reply-To: <529E109A.7050700@citrix.com>

On Tue, Dec 03, 2013 at 05:10:50PM +0000, David Vrabel wrote:
> On 03/12/13 15:40, Julien Grall wrote:
> > On ARM (32 bits and 64 bits), the double-word is 8-bytes aligned. This will
> > result on different structure from Xen and Linux repositories.
> > 
> > As Linux is using __packed__ attribute, it must have a 4-bytes padding before
> > each "id" field.
> > 
> > This change breaks guest block support with older kernel. IMHO, it's acceptable
> > because Xen on ARM is still on Tech Preview and the hypercall ABI is not yet
> > freezed.
> > 
> > Only one architecture (x86_32) doesn't have 64-bit ABI for the block interface.
> > Don't add padding if Linux is compiled for this architecture.
> 
> I'm now satisfied that this is the right thing to do.
> 
> Acked-by: David Vrabel <david.vrabel@citrix.com>

Before we go any further, I need testing confirmation that with this patch
can still run on x86 hardware the following combinations:

 32-bit guest on 64-bit dom0
 64-bit guest on 32-bit dom0

and with an 3.12 dom0

B/c I am not seeing that mentioned anywhere and I think that is creating
confusion with folks thinking it would break the x86-world (which it shouldn't).

> 
> David

  parent reply	other threads:[~2013-12-03 18:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 15:40 [PATCH v2] xen/block: Correctly define structures in public headers on ARM32 and ARM64 Julien Grall
2013-12-03 15:40 ` Julien Grall
2013-12-03 16:00 ` One Thousand Gnomes
2013-12-03 16:00 ` One Thousand Gnomes
2013-12-03 16:00   ` One Thousand Gnomes
2013-12-03 16:19   ` Julien Grall
2013-12-03 16:19   ` Julien Grall
2013-12-03 16:19     ` Julien Grall
2013-12-03 16:32     ` One Thousand Gnomes
2013-12-03 16:32       ` One Thousand Gnomes
2013-12-03 16:41       ` Ian Campbell
2013-12-03 16:41       ` Ian Campbell
2013-12-03 16:41         ` Ian Campbell
2013-12-03 17:03         ` One Thousand Gnomes
2013-12-03 17:03           ` One Thousand Gnomes
2013-12-03 18:03           ` Konrad Rzeszutek Wilk
2013-12-03 18:03             ` Konrad Rzeszutek Wilk
2013-12-03 18:03           ` Konrad Rzeszutek Wilk
2013-12-03 17:03         ` One Thousand Gnomes
2013-12-03 16:32     ` One Thousand Gnomes
2013-12-03 17:10 ` David Vrabel
2013-12-03 17:10 ` David Vrabel
2013-12-03 17:10   ` David Vrabel
2013-12-03 18:01   ` Konrad Rzeszutek Wilk
2013-12-03 18:01   ` Konrad Rzeszutek Wilk [this message]
2013-12-03 18:01     ` Konrad Rzeszutek Wilk
2013-12-12 14:19 ` [Xen-devel] " Ian Campbell
2013-12-12 14:19   ` Ian Campbell
2013-12-12 15:11   ` Roger Pau Monné
2013-12-12 15:11     ` Roger Pau Monné
2013-12-12 15:11   ` Roger Pau Monné
2013-12-12 14:19 ` Ian Campbell
  -- strict thread matches above, loose matches on Subject: below --
2013-12-03 15:40 Julien Grall

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=20131203180139.GG3734@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.