Re: [Xen-devel] linux-arm-xen branch, commit access, etc.
Hi, On 23/10/17 22:33, Stefano Stabellini wrote: On Fri, 20 Oct 2017, Julien Grall wrote: Julien, do you think we need to keep a special linux tree around for Xen on ARM testing in OSSTest or we can start using vanilla kernel releases? I would love to get rid of it, if you know of any reasons why we have to keep it, this is the time to speak :-) I think it would be better to keep aroundSome platform may be available before the code is merged. Sure. Ian, let's create a /arm/linux.git tree on xenbits where both Julien and I can push. The idea is that we'll try to use vanilla kernel releases but we'll keep it around just in case we'll need special patches for hardware support in the future. If it turns out that we don't actually need it, we can get rid of it in a year or two. We'll initialize /arm/linux.git based on the current linux-arm-xen branch. /arm/linux.git will replace linux-arm-xen in OSSTest. Sounds good? I don't mind as long as I have access to the arm linux tree. Ian do you have any opinions? Cheers, -- Julien Grall ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] linux-arm-xen branch, commit access, etc.
On Fri, 20 Oct 2017, Julien Grall wrote: > Julien, do you think we need to keep a special linux tree around for Xen > on ARM testing in OSSTest or we can start using vanilla kernel releases? > I would love to get rid of it, if you know of any reasons why we have to > keep it, this is the time to speak :-) > > > I think it would be better to keep aroundSome platform may be available > before the code is merged. Sure. Ian, let's create a /arm/linux.git tree on xenbits where both Julien and I can push. The idea is that we'll try to use vanilla kernel releases but we'll keep it around just in case we'll need special patches for hardware support in the future. If it turns out that we don't actually need it, we can get rid of it in a year or two. We'll initialize /arm/linux.git based on the current linux-arm-xen branch. /arm/linux.git will replace linux-arm-xen in OSSTest. Sounds good? Thanks, Stefano ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] linux-arm-xen branch, commit access, etc.
Hi,
Sorry for the formatting.
On 20 Oct 2017 19:06, "Stefano Stabellini" <sstabell...@kernel.org> wrote:
CC'ing Julien
On Fri, 20 Oct 2017, Ian Jackson wrote:
> Stefano Stabellini writes ("Re: [Xen-devel] linux-arm-xen branch, commit
access, etc."):
> > On Fri, 20 Oct 2017, Konrad Rzeszutek Wilk wrote:
> > > 3. Use upstream released kernels. Follow them when they are released.
> >
> > I agree with Konrad. The reason why that branch is there is that
> > initially we needed a couple of patches to run Linux on Exynos5 boards
> > (Arndale). Today, vanilla releases should work. For example, 4.13 has
> > everything we need as far as I can tell. I think it is time to remove
> > the special branch.
>
> So vanilla kernels are going to work well on our new ARM64 boxes, eg
> ThunderX, and whatever we come up with for new ARM32 testing too ?
I think so: ThunderX and other server platforms should be more
"standard" than small embedded boards. But if we decide to buy some
small and cheap ARM32 boards, such as Linaro HiKey, they tend to still
require special kernel trees.
It is what you wish :). For instance Thunder-X support has been fully made
upstream (ACPI + DT) only recently.
In other words: I think we should be able to get rid of the special tree
for the hardware that we have today, but I cannot guarantee that we
won't ever need it in the future.
IIRC we are going to get some renesas board recently. Do you know if
upstream will work?
Julien, do you think we need to keep a special linux tree around for Xen
on ARM testing in OSSTest or we can start using vanilla kernel releases?
I would love to get rid of it, if you know of any reasons why we have to
keep it, this is the time to speak :-)
I think it would be better to keep aroundSome platform may be available
before the code is merged.
Cheers,
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
Re: [Xen-devel] linux-arm-xen branch, commit access, etc.
CC'ing Julien
On Fri, 20 Oct 2017, Ian Jackson wrote:
> Stefano Stabellini writes ("Re: [Xen-devel] linux-arm-xen branch, commit
> access, etc."):
> > On Fri, 20 Oct 2017, Konrad Rzeszutek Wilk wrote:
> > > 3. Use upstream released kernels. Follow them when they are released.
> >
> > I agree with Konrad. The reason why that branch is there is that
> > initially we needed a couple of patches to run Linux on Exynos5 boards
> > (Arndale). Today, vanilla releases should work. For example, 4.13 has
> > everything we need as far as I can tell. I think it is time to remove
> > the special branch.
>
> So vanilla kernels are going to work well on our new ARM64 boxes, eg
> ThunderX, and whatever we come up with for new ARM32 testing too ?
I think so: ThunderX and other server platforms should be more
"standard" than small embedded boards. But if we decide to buy some
small and cheap ARM32 boards, such as Linaro HiKey, they tend to still
require special kernel trees.
In other words: I think we should be able to get rid of the special tree
for the hardware that we have today, but I cannot guarantee that we
won't ever need it in the future.
Julien, do you think we need to keep a special linux tree around for Xen
on ARM testing in OSSTest or we can start using vanilla kernel releases?
I would love to get rid of it, if you know of any reasons why we have to
keep it, this is the time to speak :-)
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
Re: [Xen-devel] linux-arm-xen branch, commit access, etc.
Stefano Stabellini writes ("Re: [Xen-devel] linux-arm-xen branch, commit
access, etc."):
> On Fri, 20 Oct 2017, Konrad Rzeszutek Wilk wrote:
> > 3. Use upstream released kernels. Follow them when they are released.
>
> I agree with Konrad. The reason why that branch is there is that
> initially we needed a couple of patches to run Linux on Exynos5 boards
> (Arndale). Today, vanilla releases should work. For example, 4.13 has
> everything we need as far as I can tell. I think it is time to remove
> the special branch.
So vanilla kernels are going to work well on our new ARM64 boxes, eg
ThunderX, and whatever we come up with for new ARM32 testing too ?
In.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
Re: [Xen-devel] linux-arm-xen branch, commit access, etc.
On Fri, 20 Oct 2017, Konrad Rzeszutek Wilk wrote: > On Fri, Oct 20, 2017 at 03:34:40PM +0100, Ian Jackson wrote: > > Currently we are running our ARM tests in osstest off a branch in > > Stefano's personal Linux tree. This is a bit unsatisfactory. > > > > We would like to switch to a branch that Julien can push to too, and > > that is in a more official place. > > > > There are two options: > > > > 1. Create an ARM-specific Xen tree. Currently we don't have many > > ARM-specific trees but I don't see a problem with this. So > > we could create > > /arm/linux.git > > on xenbits. > > > > 2. Use a branch name within /linux-pvops.git, the main Linux > > tree on xenbits. This would mean making Julien a committer. > > 3. Use upstream released kernels. Follow them when they are released. I agree with Konrad. The reason why that branch is there is that initially we needed a couple of patches to run Linux on Exynos5 boards (Arndale). Today, vanilla releases should work. For example, 4.13 has everything we need as far as I can tell. I think it is time to remove the special branch. If it turns out that we still need a special branch (I don't think we do), then 1. is a good option. > > What do people think would be best ? > > > > Also, separately, surely Julien should be listed in MAINTAINERS for > > the Xen ARM stuff in upstream Linux ? He doesn't seem to be at least > > in the version I have lying about here... No, that is correct, at the moment I am the only maintainer for Xen on ARM support in Linux. I'll talk to Julien but the attention it requires is very limited. Patches specific to arch/arm/xen and arch/arm64/xen/ are very few, in the order of 10 in the last year. It doesn't necessarily need more than one maintainer. ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] linux-arm-xen branch, commit access, etc.
On Fri, Oct 20, 2017 at 03:34:40PM +0100, Ian Jackson wrote: > Currently we are running our ARM tests in osstest off a branch in > Stefano's personal Linux tree. This is a bit unsatisfactory. > > We would like to switch to a branch that Julien can push to too, and > that is in a more official place. > > There are two options: > > 1. Create an ARM-specific Xen tree. Currently we don't have many > ARM-specific trees but I don't see a problem with this. So > we could create > /arm/linux.git > on xenbits. > > 2. Use a branch name within /linux-pvops.git, the main Linux > tree on xenbits. This would mean making Julien a committer. 3. Use upstream released kernels. Follow them when they are released. > > What do people think would be best ? > > Also, separately, surely Julien should be listed in MAINTAINERS for > the Xen ARM stuff in upstream Linux ? He doesn't seem to be at least > in the version I have lying about here... > > Thanks, > Ian. > > ___ > Xen-devel mailing list > Xen-devel@lists.xen.org > https://lists.xen.org/xen-devel ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
