mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vitaly Mayatskikh <v.mayatskih@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Vitaly Mayatskikh <v.mayatskih@gmail.com>,
	linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] x86: Optimize tail handling for copy_user
Date: Sat, 02 Aug 2008 00:04:48 +0200	[thread overview]
Message-ID: <m3wsj0l7cv.fsf@gravicappa.englab.brq.redhat.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0808011308470.3277@nehalem.linux-foundation.org> (Linus Torvalds's message of "Fri, 1 Aug 2008 13:10:25 -0700 (PDT)")

Linus Torvalds <torvalds@linux-foundation.org> writes:

>> Yes, I see. I was messed, sorry. Your BYTES_LEFT_IN_PAGE works very
>> well, tested.
>> 
>> Signed-off-by: Vitaly Mayatskikh <v.mayatskih@gmail.com>
>
> Ok, this latest version _looks_ ok. How well tested is it? I'm a bit 
> nervous by now. Those earlier versions that got committed had all those 
> wrone registers etc.
>
> Anyway, Ack as far as I'm concerned, but..

Well, I have sanity test for it (at http://people.redhat.com/vmayatsk/copy_user_x8664/), 
but unfortunately it shows what I want to see, not the truth. I'm going
to make a large regression testing next week.

-- 
wbr, Vitaly

  reply	other threads:[~2008-08-01 22:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 14:10 Vitaly Mayatskikh
2008-07-28 15:48 ` Linus Torvalds
2008-07-29 15:24   ` Vitaly Mayatskikh
2008-07-30 12:02   ` Vitaly Mayatskikh
2008-07-30 17:29     ` Linus Torvalds
2008-07-31 14:27       ` Vitaly Mayatskikh
2008-08-01 20:10         ` Linus Torvalds
2008-08-01 22:04           ` Vitaly Mayatskikh [this message]
2008-08-01 22:30             ` Linus Torvalds
2008-08-01 22:53               ` Vitaly Mayatskikh
2008-07-30 12:07   ` Vitaly Mayatskikh
2008-07-30 12:13   ` Vitaly Mayatskikh

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=m3wsj0l7cv.fsf@gravicappa.englab.brq.redhat.com \
    --to=v.mayatskih@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®