From: Peter Zijlstra <peterz@infradead.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
linux-stable <stable@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, LTP List <ltp@lists.linux.it>,
lkft-triage@lists.linaro.org, X86 ML <x86@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Lutomirski <luto@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: qemu-x86_64 compat: LTP: controllers: RIP: 0010:__alloc_pages
Date: Wed, 24 May 2023 19:54:42 +0200 [thread overview]
Message-ID: <20230524175442.GO4253@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CA+G9fYsP1XN31sWMtPsaXzRtiAvHsn+A2cFZS2s6+muE_Qh61Q@mail.gmail.com>
On Wed, May 24, 2023 at 09:39:50PM +0530, Naresh Kamboju wrote:
> FYI,
> These are running in AWS cloud as qemu-i386 and qemu-x86_64.
Are these hosted on x86 and using KVM or are they hosted on Graviton and
using TCG x86 ?
Supposedly TCG x86 is known 'funny' and if that's what you're using it
would be very good to confirm the problem on x86 hardware.
next prev parent reply other threads:[~2023-05-24 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 9:02 qemu-x86_64 compat: LTP: controllers: RIP: 0010:__alloc_pages Naresh Kamboju
2023-05-24 11:18 ` Arnd Bergmann
2023-05-24 12:54 ` David Laight
2023-05-24 14:07 ` Peter Zijlstra
2023-05-24 16:09 ` Naresh Kamboju
2023-05-24 17:54 ` Peter Zijlstra [this message]
2023-05-24 20:33 ` Arnd Bergmann
2023-05-25 12:22 ` Naresh Kamboju
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=20230524175442.GO4253@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=ltp@lists.linux.it \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).