On 06/07/2018 11:13 PM, Andrew Morton wrote:
On Thu, 24 May 2018 13:38:05 -0700 Andrew Morton
wrote:
Jia, Andrew,
What is the status of this patch ?
I have it scheduled for 4.18-rc1, with a cc:stable for backporting.
I'd normally put such a fix into 4.17-rcX but I'd like to give Hugh
On 06/07/2018 11:13 PM, Andrew Morton wrote:
On Thu, 24 May 2018 13:38:05 -0700 Andrew Morton
wrote:
Jia, Andrew,
What is the status of this patch ?
I have it scheduled for 4.18-rc1, with a cc:stable for backporting.
I'd normally put such a fix into 4.17-rcX but I'd like to give Hugh
Hi Andrea
Thanks for the review.
On 6/8/2018 7:38 AM, Andrea Arcangeli Wrote:
> On Thu, Jun 07, 2018 at 03:13:44PM -0700, Andrew Morton wrote:
>> This patch is quite urgent and is tagged for -stable backporting, yet
>> it remains in an unreviewed state. Any takers?
>
> It looks a
Hi Andrea
Thanks for the review.
On 6/8/2018 7:38 AM, Andrea Arcangeli Wrote:
> On Thu, Jun 07, 2018 at 03:13:44PM -0700, Andrew Morton wrote:
>> This patch is quite urgent and is tagged for -stable backporting, yet
>> it remains in an unreviewed state. Any takers?
>
> It looks a
Hi Andrew
On 6/8/2018 6:13 AM, Andrew Morton Wrote:
> On Thu, 24 May 2018 13:38:05 -0700 Andrew Morton
> wrote:
>>>
>>> Jia, Andrew,
>>>
>>> What is the status of this patch ?
>>>
>>
>> I have it scheduled for 4.18-rc1, with a cc:stable for backporting.
>>
>> I'd normally put such a fix into
Hi Andrew
On 6/8/2018 6:13 AM, Andrew Morton Wrote:
> On Thu, 24 May 2018 13:38:05 -0700 Andrew Morton
> wrote:
>>>
>>> Jia, Andrew,
>>>
>>> What is the status of this patch ?
>>>
>>
>> I have it scheduled for 4.18-rc1, with a cc:stable for backporting.
>>
>> I'd normally put such a fix into
On Thu, Jun 07, 2018 at 03:13:44PM -0700, Andrew Morton wrote:
> This patch is quite urgent and is tagged for -stable backporting, yet
> it remains in an unreviewed state. Any takers?
It looks a straightforward safe fix, on x86 hva_to_gfn_memslot would
zap those bits and hide the misalignment
On Thu, Jun 07, 2018 at 03:13:44PM -0700, Andrew Morton wrote:
> This patch is quite urgent and is tagged for -stable backporting, yet
> it remains in an unreviewed state. Any takers?
It looks a straightforward safe fix, on x86 hva_to_gfn_memslot would
zap those bits and hide the misalignment
On Thu, 24 May 2018 13:38:05 -0700 Andrew Morton
wrote:
> >
> > Jia, Andrew,
> >
> > What is the status of this patch ?
> >
>
> I have it scheduled for 4.18-rc1, with a cc:stable for backporting.
>
> I'd normally put such a fix into 4.17-rcX but I'd like to give Hugh
> time to review it and
On Thu, 24 May 2018 13:38:05 -0700 Andrew Morton
wrote:
> >
> > Jia, Andrew,
> >
> > What is the status of this patch ?
> >
>
> I have it scheduled for 4.18-rc1, with a cc:stable for backporting.
>
> I'd normally put such a fix into 4.17-rcX but I'd like to give Hugh
> time to review it and
On Thu, 24 May 2018 09:44:16 +0100 Suzuki K Poulose
wrote:
> On 14/05/18 10:45, Suzuki K Poulose wrote:
> > On 10/05/18 00:31, Andrew Morton wrote:
> >> On Fri, 4 May 2018 11:11:46 +0800 Jia He wrote:
> >>
> >>> In our armv8a server(QDF2400), I
On Thu, 24 May 2018 09:44:16 +0100 Suzuki K Poulose
wrote:
> On 14/05/18 10:45, Suzuki K Poulose wrote:
> > On 10/05/18 00:31, Andrew Morton wrote:
> >> On Fri, 4 May 2018 11:11:46 +0800 Jia He wrote:
> >>
> >>> In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by
> >>>
On 5/24/2018 5:01 PM, Suzuki K Poulose Wrote:
> On 24/05/18 09:50, Jia He wrote:
>> Hi Suzuki
>>
>> On 5/24/2018 4:44 PM, Suzuki K Poulose Wrote:
>>> On 14/05/18 10:45, Suzuki K Poulose wrote:
On 10/05/18 00:31, Andrew Morton wrote:
> On Fri, 4 May 2018 11:11:46 +0800 Jia He
On 5/24/2018 5:01 PM, Suzuki K Poulose Wrote:
> On 24/05/18 09:50, Jia He wrote:
>> Hi Suzuki
>>
>> On 5/24/2018 4:44 PM, Suzuki K Poulose Wrote:
>>> On 14/05/18 10:45, Suzuki K Poulose wrote:
On 10/05/18 00:31, Andrew Morton wrote:
> On Fri, 4 May 2018 11:11:46 +0800 Jia He wrote:
On 24/05/18 09:50, Jia He wrote:
Hi Suzuki
On 5/24/2018 4:44 PM, Suzuki K Poulose Wrote:
On 14/05/18 10:45, Suzuki K Poulose wrote:
On 10/05/18 00:31, Andrew Morton wrote:
On Fri, 4 May 2018 11:11:46 +0800 Jia He wrote:
In our armv8a server(QDF2400), I noticed lots of
On 24/05/18 09:50, Jia He wrote:
Hi Suzuki
On 5/24/2018 4:44 PM, Suzuki K Poulose Wrote:
On 14/05/18 10:45, Suzuki K Poulose wrote:
On 10/05/18 00:31, Andrew Morton wrote:
On Fri, 4 May 2018 11:11:46 +0800 Jia He wrote:
In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by
On 14/05/18 10:45, Suzuki K Poulose wrote:
On 10/05/18 00:31, Andrew Morton wrote:
On Fri, 4 May 2018 11:11:46 +0800 Jia He wrote:
In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
unaligned for rmap_item->address under memory pressure
On 14/05/18 10:45, Suzuki K Poulose wrote:
On 10/05/18 00:31, Andrew Morton wrote:
On Fri, 4 May 2018 11:11:46 +0800 Jia He wrote:
In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
unaligned for rmap_item->address under memory pressure tests(start 20 guests
and
On 10/05/18 00:31, Andrew Morton wrote:
On Fri, 4 May 2018 11:11:46 +0800 Jia He wrote:
In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
unaligned for rmap_item->address under memory pressure tests(start 20 guests
and run memhog in the host).
On 10/05/18 00:31, Andrew Morton wrote:
On Fri, 4 May 2018 11:11:46 +0800 Jia He wrote:
In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
unaligned for rmap_item->address under memory pressure tests(start 20 guests
and run memhog in the host).
...
In
On 10/05/18 02:26, Jia He wrote:
Hi Andrew
On 5/10/2018 7:31 AM, Andrew Morton Wrote:
On Fri, 4 May 2018 11:11:46 +0800 Jia He wrote:
In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
unaligned for rmap_item->address under memory pressure
On 10/05/18 02:26, Jia He wrote:
Hi Andrew
On 5/10/2018 7:31 AM, Andrew Morton Wrote:
On Fri, 4 May 2018 11:11:46 +0800 Jia He wrote:
In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
unaligned for rmap_item->address under memory pressure tests(start 20 guests
Hi Andrew
On 5/10/2018 7:31 AM, Andrew Morton Wrote:
On Fri, 4 May 2018 11:11:46 +0800 Jia He wrote:
In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
unaligned for rmap_item->address under memory pressure tests(start 20 guests
and run memhog
Hi Andrew
On 5/10/2018 7:31 AM, Andrew Morton Wrote:
On Fri, 4 May 2018 11:11:46 +0800 Jia He wrote:
In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
unaligned for rmap_item->address under memory pressure tests(start 20 guests
and run memhog in the host).
...
On Fri, 4 May 2018 11:11:46 +0800 Jia He wrote:
> In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
> unaligned for rmap_item->address under memory pressure tests(start 20 guests
> and run memhog in the host).
>
> ...
>
> In rmap_walk_ksm, the
On Fri, 4 May 2018 11:11:46 +0800 Jia He wrote:
> In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
> unaligned for rmap_item->address under memory pressure tests(start 20 guests
> and run memhog in the host).
>
> ...
>
> In rmap_walk_ksm, the rmap_item->address
[+Hugh Dickins]
Cheers,
Jia
On 5/4/2018 11:11 AM, Jia He Wrote:
In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
unaligned for rmap_item->address under memory pressure tests(start 20 guests
and run memhog in the host).
[+Hugh Dickins]
Cheers,
Jia
On 5/4/2018 11:11 AM, Jia He Wrote:
In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
unaligned for rmap_item->address under memory pressure tests(start 20 guests
and run memhog in the host).
In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
unaligned for rmap_item->address under memory pressure tests(start 20 guests
and run memhog in the host).
--begin--
[ 410.853828] WARNING: CPU: 4 PID: 4641 at
In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
unaligned for rmap_item->address under memory pressure tests(start 20 guests
and run memhog in the host).
--begin--
[ 410.853828] WARNING: CPU: 4 PID: 4641 at
30 matches
Mail list logo