linux-kernel - Re: [RFC PATCH] x86: explicit call to mmiotrace in do_page

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: <84144f020802091056hffc22eckbda461534e3a6072@mail.gmail.com>
Date:	Sat, 9 Feb 2008 20:56:07 +0200
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Pekka Paalanen" <pq@....fi>
Cc:	"Arjan van de Ven" <arjan@...radead.org>,
	"Ingo Molnar" <mingo@...e.hu>,
	"Christoph Hellwig" <hch@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] x86: explicit call to mmiotrace in do_page_fault()

Hi Pekka,

On Feb 9, 2008 8:23 PM, Pekka Paalanen <pq@....fi> wrote:
> By default it reserves 32 MB/cpu of relay buffers during module init.
> It's this big based on experimentation with the nvidia proprietary driver.
> There is no other way than unloading the module to free the buffers, or
> even to clear them. This means that every time you start the user space
> logger application, it gets old data first. Also poking the module
> parameters via /sys is not allowed.

So how is mmiotrace different from, say, blktrace that has an ioctl()
to setup/teardown the relay channels (for mmiotrace it can be a
"status" file that does the setup/teardown when written some
appropriate values)?

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