linux-kernel - Re: [PATCH 5/5] add ksm kernel shared memory driver.

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]

Date:	Mon, 20 Apr 2009 15:52:21 +0300
From:	Izik Eidus <ieidus@...hat.com>
To:	Avi Kivity <avi@...hat.com>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	kvm@...r.kernel.org, aarcange@...hat.com, chrisw@...hat.com,
	mtosatti@...hat.com, hugh@...itas.com
Subject: Re: [PATCH 5/5] add ksm kernel shared memory driver.

Avi Kivity wrote:
> Alan Cox wrote:
>> The minor number you are using already belongs to another project.
>>
>> 10,234 is free but it would be good to know what device naming is
>> proposed. I imagine other folks would like to know why you aren't using
>> sysfs or similar or extending /dev/kvm ?
>>   
>
> ksm was deliberately made independent of kvm.  While there may or may 
> not be uses of ksm without kvm (you could run ordinary qemu, but no 
> one would do this in a production deployment), keeping them separate 
> helps avoid unnecessary interdependencies.  For example all tlb 
> flushes are mediated through mmu notifiers instead of ksm hooking 
> directly into kvm.
>
Yes, beside, I do use sysfs for controlling the ksm behavior,
Ioctls are provided as easier way for application to register its memory.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/