From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
elliott@hpe.com, Brian Gerst <brgerst@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-nvdimm@ml01.01.org, x86@kernel.org
Subject: Re: [PATCH v10 3/4] x86, mce: Add __mcsafe_copy()
Date: Tue, 9 Feb 2016 15:15:57 -0800 [thread overview]
Message-ID: <20160209231557.GA23207@agluck-desk.sc.intel.com> (raw)
In-Reply-To: <20160207164933.GE5862@pd.tnic>
> You can save yourself this MOV here in what is, I'm assuming, the
> general likely case where @src is aligned and do:
>
> /* check for bad alignment of source */
> testl $7, %esi
> /* already aligned? */
> jz 102f
>
> movl %esi,%ecx
> subl $8,%ecx
> negl %ecx
> subl %ecx,%edx
> 0: movb (%rsi),%al
> movb %al,(%rdi)
> incq %rsi
> incq %rdi
> decl %ecx
> jnz 0b
The "testl $7, %esi" just checks the low three bits ... it doesn't
change %esi. But the code from the "subl $8" on down assumes that
%ecx is a number in [1..7] as the count of bytes to copy until we
achieve alignment.
So your "movl %esi,%ecx" needs to be somthing that just copies the
low three bits and zeroes the high part of %ecx. Is there a cute
way to do that in x86 assembler?
> Why aren't we pushing %r12-%r15 on the stack after the "jz 17f" above
> and using them too and thus copying a whole cacheline in one go?
>
> We would need to restore them when we're done with the cacheline-wise
> shuffle, of course.
I copied that loop from arch/x86/lib/copy_user_64.S:__copy_user_nocache()
I guess the answer depends on whether you generally copy enough
cache lines to save enough time to cover the cost of saving and
restoring those registers.
-Tony
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-02-09 23:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 20:36 [PATCH v10 0/4] Machine check recovery when kernel accesses poison Tony Luck
2015-12-31 19:40 ` [PATCH v10 2/4] x86, mce: Check for faults tagged in EXTABLE_CLASS_FAULT exception table entries Tony Luck
2016-01-08 20:49 ` [PATCH v10 1/4] x86: Expand exception table to allow new handling options Tony Luck
2016-01-08 21:18 ` [PATCH v10 3/4] x86, mce: Add __mcsafe_copy() Tony Luck
2016-02-07 16:49 ` Borislav Petkov
2016-02-09 23:15 ` Luck, Tony [this message]
2016-02-10 10:58 ` Borislav Petkov
2016-02-10 19:39 ` Luck, Tony
2016-02-10 20:50 ` Borislav Petkov
2016-02-07 16:55 ` Borislav Petkov
2016-02-07 20:54 ` Richard Weinberger
2016-01-30 0:00 ` [PATCH v10 4/4] x86: Create a new synthetic cpu capability for machine check recovery Tony Luck
2016-02-07 17:10 ` Borislav Petkov
2016-02-09 23:38 ` Luck, Tony
2016-02-10 11:06 ` Borislav Petkov
2016-02-10 19:27 ` Luck, Tony
2016-02-11 11:55 ` Borislav Petkov
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=20160209231557.GA23207@agluck-desk.sc.intel.com \
--to=tony.luck@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=elliott@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=x86@kernel.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