linux-kernel - Re: [PATCH] Add I/O hypercalls for i386 paravirt

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: <46CC2766.7020602@qumranet.com>
Date:	Wed, 22 Aug 2007 15:09:10 +0300
From:	Avi Kivity <avi@...ranet.com>
To:	Andi Kleen <ak@...e.de>
CC:	Rusty Russell <rusty@...tcorp.com.au>,
	Andrew Morton <akpm@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Chris Wright <chrisw@...s-sol.org>,
	Virtualization Mailing List <virtualization@...ts.osdl.org>
Subject: Re: [PATCH] Add I/O hypercalls for i386 paravirt

Andi Kleen wrote:
> On Wed, Aug 22, 2007 at 01:23:43PM +0300, Avi Kivity wrote:
>   
>> Andi Kleen wrote:
>>     
>>>> I don't see why it's intrusive -- they all use the APIs, right?
>>>>    
>>>>         
>>> Yes, but it still changes them. It might have a larger impact
>>> on code size for example. 
>>>  
>>>       
>> Only if CONFIG_PARAVIRT is defined.  
>>     
>
> Which eventually distribution kernels will do.
>
>   
>> And even then, all the performance 
>> sensitive stuff uses mmio, no?
>>     
>
> Not worried about performance, but just impact on code size etc.
>   

Ah.  But that's mostly modules, so real in-core changes should be very 
small (say 10 bytes per call site X 10 callsites per driver X 10 
drivers... even if off by an order of magnitude it's still tiny)


-- 
error compiling committee.c: too many arguments to function

-
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/