[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131203180333.GH3734@phenom.dumpdata.com>
Date: Tue, 3 Dec 2013 13:03:33 -0500
From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
Cc: Ian Campbell <Ian.Campbell@...rix.com>,
Julien Grall <julien.grall@...aro.org>,
xen-devel@...ts.xenproject.org, patches@...aro.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Roger Pau Monne <roger.pau@...rix.com>,
David Vrabel <david.vrabel@...rix.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Stefano Stabellini <stefano.stabellini@...citrix.com>
Subject: Re: [PATCH v2] xen/block: Correctly define structures in public
headers on ARM32 and ARM64
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists