linux-kernel - Re: [Xen-devel] [PATCH 03/11] Xen: Rename the balloon lock

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: <4A0875C7.7070305@goop.org>
Date:	Mon, 11 May 2009 12:00:23 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Isaku Yamahata <yamahata@...inux.co.jp>
CC:	Ingo Molnar <mingo@...e.hu>,
	Xen-devel <xen-devel@...ts.xensource.com>,
	the arch/x86 maintainers <x86@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
Subject: Re: [Xen-devel] [PATCH 03/11] Xen: Rename the balloon lock

Isaku Yamahata wrote:
> Hi. Please please don't move the arch common variable
> into x86 specific file. It causes link error on ia64.
>
> Before I sent the patches to fix it twice or so,
> but it seems to be dropped.
>   

Sorry, I can't seem to find them.  Could you resend?

I guess there's the larger issue of whether the 
xen_create_contiguous_region() code is also useful on ia64.  It seems to 
me the options are:

    * it is, so we should move the code somewhere common (along with the
      lock)
    * it isn't so ia64 will have its own version (in which case it can
      define its own version of the lock without much impact)
    * or we could move the lock anyway, but there's no very obvious
      place to put it

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