lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e7173f3b-6e30-03ce-74ef-291236917da3@redhat.com>
Date:   Wed, 29 Jul 2020 16:38:21 +0200
From:   David Hildenbrand <david@...hat.com>
To:     "Michael S. Tsirkin" <mst@...hat.com>,
        Andrew Morton <akpm@...ux-foundation.org>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Randy Dunlap <rdunlap@...radead.org>, broonie@...nel.org,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, linux-next@...r.kernel.org, mhocko@...e.cz,
        mm-commits@...r.kernel.org, Jason Wang <jasowang@...hat.com>
Subject: Re: mmotm 2020-07-27-18-18 uploaded (mm/page_alloc.c)

On 29.07.20 16:18, Michael S. Tsirkin wrote:
> On Tue, Jul 28, 2020 at 03:31:43PM -0700, Andrew Morton wrote:
>> On Wed, 29 Jul 2020 08:20:53 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>
>>> Hi Andrew,
>>>
>>> On Tue, 28 Jul 2020 14:55:53 -0700 Andrew Morton <akpm@...ux-foundation.org> wrote:
>>>> config CONTIG_ALLOC
>>>>         def_bool (MEMORY_ISOLATION && COMPACTION) || CMA
>>>>
>>>> says this is an improper combination.  And `make oldconfig' fixes it up.
>>>>
>>>> What's happening here?
>>>
>>> CONFIG_VIRTIO_MEM selects CONFIG_CONTIG_ALLOC ...
>>
>> Argh, select strikes again.
>>
>> So I guess VIRTIO_MEM should also select COMPACTION?
> 
> +Cc the maintainer.
> 

We had select CONFIG_CONTIG_ALLOC before and that seemed to be wrong. I
was told select might be the wrong approach.

We want memory isolation and contig_alloc with virtio-mem (which depends
on memory hot(un)plug). What would be the right way to achieve this?

-- 
Thanks,

David / dhildenb

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ