From: Guenter Roeck <linux@roeck-us.net>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 4/4] powerpc/pseries: Move dtl scanning and steal time accounting to pseries platform
Date: Mon, 10 Oct 2022 13:49:29 -0700 [thread overview]
Message-ID: <20221010204929.GA2987565@roeck-us.net> (raw)
In-Reply-To: <20220902085316.2071519-5-npiggin@gmail.com>
On Fri, Sep 02, 2022 at 06:53:16PM +1000, Nicholas Piggin wrote:
> dtl is the PAPR Dispatch Trace Log, which is entirely a pseries feature.
> The pseries platform alrady has a file dealing with the dtl, so move
> scanning for stolen time accounting there from kernel/time.c.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
This patch ties DTL to PPC_SPLPAR without updating configuration
dependencies. As result, the following build error may now be seen
if CONFIG_PPC_SPLPAR=y and CONFIG_DTL=n.
arch/powerpc/kernel/irq.o: in function `.do_IRQ':
irq.c:(.text+0x2798): undefined reference to `.pseries_accumulate_stolen_time'
I updated my own configurations to avoid the problem, but you might see
randconfig failures with this error in the future.
Guenter
next prev parent reply other threads:[~2022-10-10 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 8:53 [PATCH v2 0/4] powerpc: stolen time accounting for VIRT_CPU_ACCOUNTING_GEN Nicholas Piggin
2022-09-02 8:53 ` [PATCH v2 1/4] powerpc/pseries: Add wait interval counter definitions to struct lppaca Nicholas Piggin
2022-09-02 8:53 ` [PATCH v2 2/4] powerpc/pseries: Implement CONFIG_PARAVIRT_TIME_ACCOUNTING Nicholas Piggin
2022-09-02 8:53 ` [PATCH v2 3/4] powerpc/64: Remove PPC64 special case for cputime accounting default Nicholas Piggin
2022-09-02 8:53 ` [PATCH v2 4/4] powerpc/pseries: Move dtl scanning and steal time accounting to pseries platform Nicholas Piggin
2022-10-10 20:49 ` Guenter Roeck [this message]
2022-09-09 12:06 ` [PATCH v2 0/4] powerpc: stolen time accounting for VIRT_CPU_ACCOUNTING_GEN Michael Ellerman
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=20221010204929.GA2987565@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
/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).