From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Ostrovsky Subject: Re: [PATCH v5 00/22] xen/arm64: Add support for 64KB page in Linux Date: Fri, 2 Oct 2015 09:25:15 -0400 Message-ID: <560E85BB.4000101@oracle.com> References: <1443609937-25278-1-git-send-email-julien.grall@citrix.com> <560D4E02.60700@citrix.com> <1443779494.11707.71.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Zi0L1-0004Db-Rp for xen-devel@lists.xenproject.org; Fri, 02 Oct 2015 13:25:27 +0000 In-Reply-To: <1443779494.11707.71.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell , David Vrabel , Konrad Rzeszutek Wilk Cc: xen-devel@lists.xenproject.org, Ian.Jackson@eu.citrix.com List-Id: xen-devel@lists.xenproject.org On 10/02/2015 05:51 AM, Ian Campbell wrote: > (trimming and reordering To/Cc) > > On Thu, 2015-10-01 at 16:15 +0100, David Vrabel wrote: >> On 30/09/15 11:45, Julien Grall wrote: >>> Hi all, >>> >>> ARM64 Linux is supporting both 4KB and 64KB page granularity. Although, >>> Xen >>> hypercall interface and PV protocol are always based on 4KB page >>> granularity. >>> >>> Any attempt to boot a Linux guest with 64KB pages enabled will result >>> to a >>> guest crash. >>> >>> This series is a first attempt to allow those Linux running with the >>> current >>> hypercall interface and PV protocol. >>> >>> This solution has been chosen because we want to run Linux 64KB in >>> released >>> Xen ARM version or/and platform using an old version of Linux DOM0. >> Applied to for-linus-4.4, thanks. >> >> Boris, can you kick off a set of tests for this branch, please? > @Boris, > > Would it be possible to have the results of this test framework posted to > the list, like osstest does? Not in the way it is currently set up --- we have 7 or 8 test systems and each one generates an email with results. It may not be too bad if all tests pass but if they fail each email may have as much as 2-3 MB of logs (we don't upload them anywhere). I could generate a summary of a nightly run but then we have some intermittent failures mostly on some older distros (like Fedora 15) that we are unlikely to ever look into so that may make things confusing (Yes, the question is then -- why do we even bother running it). > > @Linux-Maintainers, > > It occurs to me that osstest doesn't have a branch which is testing your > kernel tree. Do you have a fast-forwarding branch in git > ://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git which merges up some > forward looking set of changes? If so I can pretty trivially arrange an > osstest branch to track it. > > (If there isn't a f-forwarding one maybe it would still be worth testing > something, it just probably wouldn't get bisected in any useful way if it > broke). Yes, perhaps have a devel/oss branch that tracks the latest devel/for-linus-? David? -boris