All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Feng Kan OS <fengkan@os.amperecomputing.com>,
	Vishnu Pajjuri OS <vishnu@os.amperecomputing.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH] xen/arm: p2m: configure pa_range_info table to support 42 bit PA systems.
Date: Mon, 8 Apr 2019 13:07:45 +0100	[thread overview]
Message-ID: <3c0153aa-0662-c51f-039c-2beb7eaaa34d@arm.com> (raw)
In-Reply-To: <21628b60-483a-69e5-cc5e-7c5ec98f93a7@os.amperecomputing.com>

Hi,

On 3/15/19 11:57 PM, Feng Kan OS wrote:
> Thanks Julien.
> 
> On 3/15/19 4:21 AM, Julien Grall wrote:
>> Hi,
>>
>> Thank you for posting the patch.
>>
>> Title: No need for full stop in the commit title.
>>
>> On 15/03/2019 08:34, Vishnu Pajjuri OS wrote:
>> I can't remember which other platforms support 42-bits PA. I think at
>> that time it was X-Gene. As long as no current embedded platform we
>> support use 42-bit PA, this change may be ok. Stefano do you recall what
>> was the platform?
> Ampere eMAG platform is essentially the continuation of X-Gene. These
> systems are targeted as servers with upto 1TB of RAM.
>>
>> In any case, the new behavior (and consequence) needs to be clearly
>> explained in the commit message.
> Got it, we will resubmit if Stefano is okay with the change.

To make progress on this patch, I would suggest to resubmit it with the 
changes requested.

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

WARNING: multiple messages have this Message-ID (diff)
From: Julien Grall <julien.grall@arm.com>
To: Feng Kan OS <fengkan@os.amperecomputing.com>,
	Vishnu Pajjuri OS <vishnu@os.amperecomputing.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen/arm: p2m: configure pa_range_info table to support 42 bit PA systems.
Date: Mon, 8 Apr 2019 13:07:45 +0100	[thread overview]
Message-ID: <3c0153aa-0662-c51f-039c-2beb7eaaa34d@arm.com> (raw)
Message-ID: <20190408120745.nmwsozH1_uk1EUxeo-bkvJhLeWgonQLJFiiO2SZsKjo@z> (raw)
In-Reply-To: <21628b60-483a-69e5-cc5e-7c5ec98f93a7@os.amperecomputing.com>

Hi,

On 3/15/19 11:57 PM, Feng Kan OS wrote:
> Thanks Julien.
> 
> On 3/15/19 4:21 AM, Julien Grall wrote:
>> Hi,
>>
>> Thank you for posting the patch.
>>
>> Title: No need for full stop in the commit title.
>>
>> On 15/03/2019 08:34, Vishnu Pajjuri OS wrote:
>> I can't remember which other platforms support 42-bits PA. I think at
>> that time it was X-Gene. As long as no current embedded platform we
>> support use 42-bit PA, this change may be ok. Stefano do you recall what
>> was the platform?
> Ampere eMAG platform is essentially the continuation of X-Gene. These
> systems are targeted as servers with upto 1TB of RAM.
>>
>> In any case, the new behavior (and consequence) needs to be clearly
>> explained in the commit message.
> Got it, we will resubmit if Stefano is okay with the change.

To make progress on this patch, I would suggest to resubmit it with the 
changes requested.

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2019-04-08 12:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15  8:34 [PATCH] xen/arm: p2m: configure pa_range_info table to support 42 bit PA systems Vishnu Pajjuri OS
2019-03-15 11:21 ` Julien Grall
2019-03-15 23:57   ` Feng Kan OS
2019-03-18 11:05     ` Julien Grall
2019-03-19 16:55       ` Feng Kan OS
2019-04-08 12:07     ` Julien Grall [this message]
2019-04-08 12:07       ` [Xen-devel] " Julien Grall
2019-04-16 22:42       ` Stefano Stabellini
2019-04-16 22:42         ` [Xen-devel] " Stefano Stabellini

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=3c0153aa-0662-c51f-039c-2beb7eaaa34d@arm.com \
    --to=julien.grall@arm.com \
    --cc=fengkan@os.amperecomputing.com \
    --cc=sstabellini@kernel.org \
    --cc=vishnu@os.amperecomputing.com \
    --cc=xen-devel@lists.xenproject.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.