From: firstname.lastname@example.org To: Ingo Molnar <email@example.com> Cc: Andrew Lutomirski <firstname.lastname@example.org>, email@example.com, Thomas Gleixner <firstname.lastname@example.org>, email@example.com, Jesper Juhl <firstname.lastname@example.org>, Borislav Petkov <email@example.com>, Linus Torvalds <firstname.lastname@example.org>, Andrew Morton <email@example.com>, Arjan van de Ven <firstname.lastname@example.org>, Jan Beulich <JBeulich@novell.com>, richard -rw- weinberger <email@example.com>, Mikael Pettersson <firstname.lastname@example.org>, Andi Kleen <email@example.com>, Brian Gerst <firstname.lastname@example.org>, Louis Rilling <Louis.Rilling@kerlabs.com>, Valdis.Kletnieks@vt.edu Subject: Re: [PATCH v5 8/9] x86-64: Emulate legacy vsyscalls Date: Wed, 08 Jun 2011 11:29:37 +0200 Message-ID: <4DEF4101.17745.1C109461@pageexec.freemail.hu> (raw) In-Reply-To: <20110608071620.GB6747@elte.hu> On 8 Jun 2011 at 9:16, Ingo Molnar wrote: > The thing is, as i explained it before, your claim: > > > a page fault is never a fast path > > is simply ridiculous on its face and crazy talk. you didn't *explain* a thing. you *claimed* something but offered *no* proof. where's your measurement showing the single cycle improvement? how many times do i get to ask you for it before you're willing to provide it? does it even exist? you see, i'm beginning to think that you simply just made up that claim, or in plain english, you lied about it. is that really the case? > Beyond all the reasons why we don't want to touch the page fault path > we have a working, implemented, tested IDT based alternative approach > here that is faster btw, the pf based approach can be made as fast as well since the necessary checks can be moved up early. but then we'll face the single cycle brigade ;). > and more compartmented what does that even mean here? the pf based approach is less code btw. > Even if you do not take my word for it, several prominent kernel > developers told you already that you are wrong, you must have been reading a different thread or i wasn't cc'd on those claims. care to quote them back (i only remember Pekka's mail and he has yet to back up his claim about single/low cycle counts being important for the bootup case)? also claiming something and proving something are different things. as i told you already, ex cathedra statements don't work here. > and i also showed you the commits that prove you wrong. unfounded single cycle improvement claims don't a proof make. show your measurements instead. provided they exist that is. > Your reply to that was to try to change the topic, what change are you talking about? you insisted on calling the pf path fast and your single cycle improvements relevant, you get to prove it. > laced with frequent insults thrown at me. You called me an 'asshole' yet > the only thing i did was that i argued with you patiently. i wish you had argued (i.e., presented well thought out, true and releavant statements) but instead you only threw out completely baseless accusations, insinuations, or even outright lies, never mind the several ad hominem statements that i generously overlooked since unlike you, i can handle the heat of a discussion ;). IOW, stop pretending to be the hurt angel here, you're very far from it. > Is there *any* point where you are willing to admit that you are > wrong or should i just start filtering out your emails to save me all > this trouble? sure, just prove me wrong on a claim and i'll admit it ;). > When you comment on technical details you generally > make very good suggestions so i'd hate to stop listening to your > feedback, but there's a S/N ratio threshold under which i will need > to do it ... you sound like i care about who you listen to. if you're a mature person you might as well act as one. like start answering the questions i posed you in the last round of emails then we'll see about that S/N ratio.
next prev parent reply index Thread overview: 112+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-05 17:50 [PATCH v5 0/9] Remove syscall instructions at fixed addresses Andy Lutomirski 2011-06-05 17:50 ` [PATCH v5 1/9] x86-64: Fix alignment of jiffies variable Andy Lutomirski 2011-06-06 8:31 ` [tip:x86/vdso] " tip-bot for Andy Lutomirski 2011-06-05 17:50 ` [PATCH v5 2/9] x86-64: Document some of entry_64.S Andy Lutomirski 2011-06-06 8:31 ` [tip:x86/vdso] " tip-bot for Andy Lutomirski 2011-06-05 17:50 ` [PATCH v5 3/9] x86-64: Give vvars their own page Andy Lutomirski 2011-06-06 8:32 ` [tip:x86/vdso] " tip-bot for Andy Lutomirski 2011-06-05 17:50 ` [PATCH v5 4/9] x86-64: Remove kernel.vsyscall64 sysctl Andy Lutomirski 2011-06-06 8:32 ` [tip:x86/vdso] " tip-bot for Andy Lutomirski 2011-12-05 18:27 ` [PATCH v5 4/9] " Matthew Maurer 2011-06-05 17:50 ` [PATCH v5 5/9] x86-64: Map the HPET NX Andy Lutomirski 2011-06-06 8:33 ` [tip:x86/vdso] " tip-bot for Andy Lutomirski 2011-06-05 17:50 ` [PATCH v5 6/9] x86-64: Remove vsyscall number 3 (venosys) Andy Lutomirski 2011-06-06 8:33 ` [tip:x86/vdso] " tip-bot for Andy Lutomirski 2011-06-05 17:50 ` [PATCH v5 7/9] x86-64: Fill unused parts of the vsyscall page with 0xcc Andy Lutomirski 2011-06-06 8:34 ` [tip:x86/vdso] " tip-bot for Andy Lutomirski 2011-06-05 17:50 ` [PATCH v5 8/9] x86-64: Emulate legacy vsyscalls Andy Lutomirski 2011-06-05 19:30 ` Ingo Molnar 2011-06-05 20:01 ` Andrew Lutomirski 2011-06-06 7:39 ` Ingo Molnar 2011-06-06 9:42 ` pageexec 2011-06-06 11:19 ` Andrew Lutomirski 2011-06-06 11:56 ` pageexec 2011-06-06 12:43 ` Andrew Lutomirski 2011-06-06 13:58 ` pageexec 2011-06-06 14:07 ` Brian Gerst 2011-06-07 23:32 ` pageexec 2011-06-07 23:49 ` Andrew Lutomirski 2011-06-08 6:32 ` pageexec 2011-06-06 15:26 ` Ingo Molnar 2011-06-06 15:48 ` pageexec 2011-06-06 15:59 ` Ingo Molnar 2011-06-06 16:19 ` pageexec 2011-06-06 16:47 ` Ingo Molnar 2011-06-06 22:49 ` pageexec 2011-06-06 22:57 ` david 2011-06-07 9:07 ` Ingo Molnar 2011-06-07 6:59 ` Pekka Enberg 2011-06-07 8:30 ` Ingo Molnar 2011-06-07 23:24 ` pageexec 2011-06-08 5:55 ` Pekka Enberg 2011-06-08 6:19 ` pageexec 2011-06-08 6:48 ` Ingo Molnar 2011-06-08 9:02 ` pageexec 2011-06-08 9:11 ` Andi Kleen 2011-06-08 9:35 ` pageexec 2011-06-08 10:06 ` Andi Kleen 2011-06-08 10:26 ` pageexec 2011-06-08 10:39 ` Ingo Molnar 2011-06-08 10:35 ` Ingo Molnar 2011-06-08 9:15 ` Ingo Molnar 2011-06-08 7:16 ` Ingo Molnar 2011-06-08 9:29 ` pageexec [this message] 2011-06-06 14:01 ` Linus Torvalds 2011-06-06 14:55 ` pageexec 2011-06-06 15:33 ` Ingo Molnar 2011-06-06 15:58 ` pageexec 2011-06-06 15:41 ` Ingo Molnar 2011-06-06 8:34 ` [tip:x86/vdso] " tip-bot for Andy Lutomirski 2011-06-06 8:35 ` [tip:x86/vdso] x86-64, vdso, seccomp: Fix !CONFIG_SECCOMP build tip-bot for Ingo Molnar 2011-06-07 7:49 ` [tip:x86/vdso] x86-64: Emulate legacy vsyscalls tip-bot for Andy Lutomirski 2011-06-07 8:03 ` tip-bot for Andy Lutomirski 2011-06-05 17:50 ` [PATCH v5 9/9] x86-64: Add CONFIG_UNSAFE_VSYSCALLS to feature-removal-schedule Andy Lutomirski 2011-06-06 8:34 ` [tip:x86/vdso] " tip-bot for Andy Lutomirski 2011-06-06 8:46 ` [PATCH v5 9/9] " Linus Torvalds 2011-06-06 9:31 ` Andi Kleen 2011-06-06 10:39 ` pageexec 2011-06-06 13:56 ` Linus Torvalds 2011-06-06 18:46 ` pageexec 2011-06-06 20:40 ` Linus Torvalds 2011-06-06 20:51 ` Andrew Lutomirski 2011-06-06 21:54 ` Ingo Molnar 2011-06-06 21:45 ` Ingo Molnar 2011-06-06 21:48 ` Ingo Molnar [not found] ` <BANLkTi==uw_h78oaep1cCOCzwY0edLUU_Q@mail.gmail.com> 2011-06-07 8:03 ` [PATCH, v6] x86-64: Emulate legacy vsyscalls Ingo Molnar 2011-06-06 21:53 ` [PATCH v5 9/9] x86-64: Add CONFIG_UNSAFE_VSYSCALLS to feature-removal-schedule pageexec 2011-06-06 14:44 ` Ingo Molnar 2011-06-06 15:01 ` pageexec 2011-06-06 15:15 ` Ingo Molnar 2011-06-06 15:29 ` pageexec 2011-06-06 16:54 ` Ingo Molnar 2011-06-06 18:59 ` pageexec 2011-06-06 19:25 ` Ingo Molnar 2011-06-07 0:34 ` pageexec 2011-06-07 9:51 ` Ingo Molnar 2011-06-07 23:24 ` pageexec 2011-06-10 11:19 ` Ingo Molnar 2011-06-14 0:48 ` pageexec 2011-06-15 19:42 ` Valdis.Kletnieks 2011-06-06 14:52 ` Ingo Molnar 2011-06-06 10:24 ` [PATCH] x86-64, vsyscalls: Rename UNSAFE_VSYSCALLS to COMPAT_VSYSCALLS Ingo Molnar 2011-06-06 11:20 ` pageexec 2011-06-06 12:47 ` Ingo Molnar 2011-06-06 12:48 ` Ingo Molnar 2011-06-06 18:04 ` pageexec 2011-06-06 19:12 ` Ingo Molnar 2011-06-07 0:02 ` pageexec 2011-06-07 9:56 ` Ingo Molnar 2011-06-07 23:24 ` pageexec 2011-06-09 6:48 ` Ingo Molnar 2011-06-09 23:33 ` pageexec 2011-06-07 10:05 ` Ingo Molnar 2011-06-07 23:24 ` pageexec 2011-06-09 7:02 ` Ingo Molnar 2011-06-09 23:33 ` pageexec 2011-06-07 10:13 ` Ingo Molnar 2011-06-07 23:24 ` pageexec 2011-06-06 12:19 ` Ted Ts'o 2011-06-06 12:33 ` Andrew Lutomirski 2011-06-06 12:37 ` Ingo Molnar 2011-06-06 14:34 ` [tip:x86/vdso] " tip-bot for Ingo Molnar 2011-06-05 20:05 ` [PATCH v5 0/9] Remove syscall instructions at fixed addresses Andrew Lutomirski
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4DEF4101.17745.1C109461@pageexec.freemail.hu \ --email@example.com \ --cc=JBeulich@novell.com \ --cc=Louis.Rilling@kerlabs.com \ --cc=Valdis.Kletnieks@vt.edu \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
LKML Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \ firstname.lastname@example.org public-inbox-index lkml Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git