linux-kernel - Re: Comments on UV tlb flushing

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: <20080729133204.GA13138@sgi.com>
Date:	Tue, 29 Jul 2008 08:32:04 -0500
From:	Cliff Wickman <cpw@....com>
To:	Nick Piggin <nickpiggin@...oo.com.au>, jeremy@...p.org
Cc:	steiner@....com, mingo@...e.hu, linux-kernel@...r.kernel.org
Subject: Re: Comments on UV tlb flushing

On Tue, Jul 29, 2008 at 02:12:18PM +1000, Nick Piggin wrote:
> On Tuesday 29 July 2008 10:28, Jeremy Fitzhardinge wrote:
> > I'm just reworking the x86 tlb code to use smp_call_function_mask, and I
> > see how the UV tlb flushing hooks in.  A few things occur to me:
> >
> >    1. There should be a CONFIG_X86_UV to select this code.  tlb_uv.o is
> >       around 6k, which is not trivial overhead to subject every x86_64
> >       kernel to.
> 
> Definitely.

I'd like to talk about this issue separate from the virtualization one.

I think that the Linux distributions are not going to build a special
UV kernel, are they?  So every distro would have to be prompted to 
turn on CONFIG_X86_UV, or else their kernel is not going to boot on UV.

But you have a point about not linking the 6k UV object file where 
size is an issue.
Thanks for catching that.

Perhaps the UV code should be excluded if CONFIG_EMBEDDED is set.

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