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:03:33 -0500	[thread overview]
Message-ID: <20131203180333.GH3734@phenom.dumpdata.com> (raw)
In-Reply-To: <20131203170310.7099a706@alan.etchedpixels.co.uk>

On Tue, Dec 03, 2013 at 05:03:10PM +0000, One Thousand Gnomes wrote:
> > itself. The protocol is defined by an entity which is external to Linux.
> > If this had been a bug in the IP protocol handling we would fix it and
> > move on. This case is no different IMHO.
> 
> Actually that is quite untrue. We are *very* careful that we can talk to
> other internet nodes that speak broken versions of TCP. There have even
> been changes made to protocol definitions during initial research to
> avoid tripping bugs in existing implementations.
> 
> > Once we set the ABI in stone then this is the sort of thing we will care
> > very much about (as we have done for many years on x86). Until then it
> > is not.
> 
> Maybe Xen doesn't, but perhaps Linux doesn't wish to be tarred with the
> same brush. What Xen decides is the official protocol is Xen's decision.
> What a Linux guest does to keep compatibility ought to follow what Linux
> does as policy.

I believe that this patch does not alter the x86 protocols.
Only the ARM based ones which are still in Technical Preview.

> 
> Alan

WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	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>,
	David Vrabel <david.vrabel@citrix.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.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:03:33 -0500	[thread overview]
Message-ID: <20131203180333.GH3734@phenom.dumpdata.com> (raw)
In-Reply-To: <20131203170310.7099a706@alan.etchedpixels.co.uk>

On Tue, Dec 03, 2013 at 05:03:10PM +0000, One Thousand Gnomes wrote:
> > itself. The protocol is defined by an entity which is external to Linux.
> > If this had been a bug in the IP protocol handling we would fix it and
> > move on. This case is no different IMHO.
> 
> Actually that is quite untrue. We are *very* careful that we can talk to
> other internet nodes that speak broken versions of TCP. There have even
> been changes made to protocol definitions during initial research to
> avoid tripping bugs in existing implementations.
> 
> > Once we set the ABI in stone then this is the sort of thing we will care
> > very much about (as we have done for many years on x86). Until then it
> > is not.
> 
> Maybe Xen doesn't, but perhaps Linux doesn't wish to be tarred with the
> same brush. What Xen decides is the official protocol is Xen's decision.
> What a Linux guest does to keep compatibility ought to follow what Linux
> does as policy.

I believe that this patch does not alter the x86 protocols.
Only the ARM based ones which are still in Technical Preview.

> 
> Alan

  reply	other threads:[~2013-12-03 18:03 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: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 17:03         ` One Thousand Gnomes
2013-12-03 17:03           ` One Thousand Gnomes
2013-12-03 18:03           ` Konrad Rzeszutek Wilk [this message]
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:41       ` Ian Campbell
2013-12-03 16:32     ` One Thousand Gnomes
2013-12-03 16:19   ` Julien Grall
2013-12-03 16:00 ` One Thousand Gnomes
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
2013-12-03 18:01   ` Konrad Rzeszutek Wilk
2013-12-03 17:10 ` David Vrabel
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   ` [Xen-devel] " 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=20131203180333.GH3734@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.