From: Peter Zijlstra <peterz@infradead.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
x86@kernel.org
Subject: Re: [tip: x86/urgent] x86/mm: Fix pti_clone_entry_text() for i386
Date: Tue, 6 Aug 2024 17:05:15 +0200 [thread overview]
Message-ID: <20240806150515.GS39708@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20240806145632.GR39708@noisy.programming.kicks-ass.net>
On Tue, Aug 06, 2024 at 04:56:32PM +0200, Peter Zijlstra wrote:
> On Tue, Aug 06, 2024 at 07:25:42AM -0700, Guenter Roeck wrote:
>
> > I created http://server.roeck-us.net/qemu/x86-v6.11-rc2/ with all
> > the relevant information. Please let me know if you need anything else.
>
> So I grabbed that config, stuck it in the build dir I used last time and
> upgraded gcc-13 from 13.2 ro 13.3. But alas, my build runs successfully
> :/
>
> Is there anything else special I missed?
run.sh is not exacrlty the same this time, different CPU model, that
made it go.
OK, lemme poke at this.
next prev parent reply other threads:[~2024-08-06 15:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 10:55 [tip: x86/urgent] x86/mm: Fix pti_clone_entry_text() for i386 tip-bot2 for Peter Zijlstra
2024-08-06 4:52 ` Guenter Roeck
2024-08-06 8:50 ` Peter Zijlstra
2024-08-06 14:25 ` Guenter Roeck
2024-08-06 14:56 ` Peter Zijlstra
2024-08-06 15:05 ` Peter Zijlstra [this message]
2024-08-06 15:46 ` Peter Zijlstra
2024-08-06 15:59 ` Peter Zijlstra
2024-08-06 16:42 ` Guenter Roeck
2024-08-06 18:48 ` Peter Zijlstra
2024-08-06 19:12 ` Guenter Roeck
2024-08-06 20:16 ` Guenter Roeck
2024-08-07 13:51 ` [tip: x86/urgent] x86/mm: Fix PTI for i386 some more tip-bot2 for Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2024-08-01 13:03 [tip: x86/urgent] x86/mm: Fix pti_clone_entry_text() for i386 tip-bot2 for Peter Zijlstra
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=20240806150515.GS39708@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=linux@roeck-us.net \
--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