linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	"buddy.zhang" <buddy.zhang@biscuitos.cn>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Venkatesh Pallipadi <venki@google.com>,
	Suresh Siddha <sbsiddha@gmail.com>,
	Juergen Gross <jgross@suse.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Konstantin Khlebnikov <khlebnikov@openvz.org>
Subject: Re: [PATCH] mm: Keep memory type same on DEVMEM Page-Fault
Date: Wed, 28 Jun 2023 11:10:34 +0200	[thread overview]
Message-ID: <cacb6af0-27a8-8dc4-39dc-fc3936ea54eb@redhat.com> (raw)
In-Reply-To: <20230619131417.42d4e73d1b7669162ea44e29@linux-foundation.org>

On 19.06.23 22:14, Andrew Morton wrote:
> On Sun, 16 Apr 2023 11:39:44 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> 
>> On Wed, 12 Apr 2023 14:22:36 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>>
>>> On Sun, 19 Mar 2023 11:37:50 +0800 "buddy.zhang" <buddy.zhang@biscuitos.cn> wrote:
>>>
>>>> On X86 architecture, supports memory type on Page-table, such as
>>>> PTE is PAT/PCD/PWD, which can setup up Memory Type as WC/WB/WT/UC etc.
>>>> Then, Virtual address from userspace or kernel space can map to
>>>> same physical page, if each page table has different memory type,
>>>> then it's confused to have more memory type for same physical page.
>>>
>>> Thanks.  Nobody has worked on this code for a long time.  I'll cc a few
>>> folks who may be able to comment.
>>>
>>
>> Well that didn't go very well.
>>
>> Buddy, can you please explain what are the user-visible effects of the
>> bug?  Does the kernel crash?  Memory corruption, etc?  Thanks.
>>
> 
> Anyone?
> 

With a clear problem description, ad requested by you, I could be 
motivated to review this and understand the details :)

-- 
Cheers,

David / dhildenb



      reply	other threads:[~2023-06-28  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19  3:37 [PATCH] mm: Keep memory type same on DEVMEM Page-Fault buddy.zhang
2023-04-12 21:22 ` Andrew Morton
2023-04-16 18:39   ` Andrew Morton
2023-06-19 20:14     ` Andrew Morton
2023-06-28  9:10       ` David Hildenbrand [this message]

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=cacb6af0-27a8-8dc4-39dc-fc3936ea54eb@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=buddy.zhang@biscuitos.cn \
    --cc=dan.j.williams@intel.com \
    --cc=jgross@suse.com \
    --cc=khlebnikov@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sbsiddha@gmail.com \
    --cc=venki@google.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).