linux-kernel - Re: [PATCH -rt] CONFIG_PARAVIRT and CONFIG

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: <20070622153232.GA31848@elte.hu>
Date:	Fri, 22 Jun 2007 17:32:32 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Chris Wright <chrisw@...s-sol.org>
Cc:	Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
	linux-rt-users@...r.kernel.org
Subject: Re: [PATCH -rt] CONFIG_PARAVIRT and CONFIG_MCOUNT don't play well
	together


* Chris Wright <chrisw@...s-sol.org> wrote:

> > thanks! I ran into this before and asked for the fastcalls to not be 
> > removed from upstream paravirt.c but to no avail it seems. It does 
> > no harm to anyone to keep the 'fastcall' declarations and 
> > definitions for places where _actual assembly code_ depends on the 
> > calling convention. Could someone please send this upstream-wards 
> > too?
> 
> Yes, I agree, it's actually documenting the subtlety of the calling 
> convention, not just noise in the source.  The upstream patch is 
> different, I'll sort one out.

great!

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