From: Peter Zijlstra <peterz@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Hansen <dave.hansen@intel.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
kirill.shutemov@linux.intel.com
Subject: Re: [GIT PULL] x86/mm for 6.4
Date: Wed, 3 May 2023 21:01:47 +0200 [thread overview]
Message-ID: <20230503190147.GA1719388@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAHk-=wgokAgkTVpEHM7c8oP9mca5s21RcxksF8h3FwWFJbCu3w@mail.gmail.com>
On Wed, May 03, 2023 at 10:54:38AM -0700, Linus Torvalds wrote:
> On Wed, May 3, 2023 at 9:38 AM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > So I'm going to just remove the 'sign' games entirely. They are
> > completely broken in 'untagged_addr_remote()', they _used_ to be
> > completely broken in 'untagged_addr()', and it looks like it's all
> > unnecessary.
>
> Ok, I've pushed out my changes to the 'x86-uaccess-cleanup' branch.
>
> I think it's all good, but it would be really nice to hear it's been
> tested on a setup that actually has LAM (simulator? or maybe there is
> actual hw inside Intel)
>
> And any other commentary is appreciated,
Looks sane from a first reading. But I'll try and have another look
tomorrow.
Also per how 2s complement is constructed 0 has to be in the positive
space for it to be 'half'. Also, typically 0 is included in N and the
traditional 'positive integers' set is then written as N \ {0}, but
that's somewhat modern and a lot of variation exists -- although
typically books tend to specify where they stand on that issue.
I suppose that's a very long winded way of saying, that yes, ofcourse 0
is a positive number :-)
next prev parent reply other threads:[~2023-05-03 19:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 22:56 [GIT PULL] x86/mm for 6.4 Dave Hansen
2023-04-28 17:23 ` pr-tracker-bot
2023-04-28 20:07 ` Linus Torvalds
2023-04-28 20:15 ` Linus Torvalds
2023-04-29 0:38 ` Kirill A. Shutemov
2023-04-29 1:04 ` Linus Torvalds
2023-05-02 15:42 ` Dave Hansen
2023-05-02 16:00 ` Linus Torvalds
2023-05-02 20:14 ` Linus Torvalds
2023-05-03 0:53 ` Dave Hansen
2023-05-03 1:17 ` Linus Torvalds
2023-05-03 16:38 ` Linus Torvalds
2023-05-03 16:44 ` Dave Hansen
2023-05-03 16:51 ` Linus Torvalds
2023-05-03 17:54 ` Linus Torvalds
2023-05-03 19:01 ` Peter Zijlstra [this message]
2023-05-03 19:19 ` Linus Torvalds
2023-05-05 19:56 ` Linus Torvalds
2023-05-05 20:59 ` Kirill A. Shutemov
2023-05-04 6:28 ` Kirill A. Shutemov
2023-05-04 15:25 ` Dave Hansen
2023-05-04 17:10 ` Kirill A. Shutemov
2023-05-04 17:10 ` Linus Torvalds
2023-05-03 8:01 ` Peter Zijlstra
2023-05-03 16:38 ` Linus Torvalds
2023-06-16 8:47 ` Alexander Potapenko
2023-06-16 16:22 ` Linus Torvalds
2023-06-19 12:03 ` Alexander Potapenko
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=20230503190147.GA1719388@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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