From: Sudeep Holla <sudeep.holla@arm.com>
To: Song Shuai <suagrfillet@gmail.com>
Cc: gregkh@linuxfoundation.org, rafael@kernel.org,
conor.dooley@microchip.com, ionela.voinescu@arm.com,
Sudeep Holla <sudeep.holla@arm.com>,
Pierre.Gondois@arm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] arch_topology: Clear LLC sibling when cacheinfo teardown
Date: Mon, 20 Mar 2023 07:20:29 +0000 [thread overview]
Message-ID: <20230320072029.j6wsdpmmq7gmlvhg@bogus> (raw)
In-Reply-To: <CAAYs2=gtgcKthFyb=Vz6VJZamyfedoXJRXfsrAtLzj0-d=D89w@mail.gmail.com>
On Mon, Mar 20, 2023 at 06:20:34AM +0000, Song Shuai wrote:
>
> My original point is to clear the llc_sibling right after clearing of
> share_cpu_map like what you did in 3fcbf1c77d08.
>
Yes I understood that. There were other issues that were fixed later
and hence the state of current code.
> And the ~~issue~~ I described above was found when I manually tested
> the 'base/cacheinfo:online' hpstate, which can be triggered by the
> following commands:
>
> ```
> hpid=$(sed -n '/cacheinfo/s/:.*//p' /sys/devices/system/cpu/hotplug/states)
> echo $((hpid-1)) > /sys/devices/system/cpu/cpu2/hotplug/target
>
> ```
>
Thanks for the detailed steps. I had guessed something very similar.
> Anyway, the short inconsistency window you explained seems acceptable to me.
>
Yes just inconsistency but technically the CPU topology is still correct
including LLC information. I don't see a point in clearing the cacheinfo
at this point and just couple of hotplug state later reset all the topology
as the CPU is being removed. I feel it to be redundant and we can add if
we absolutely need it(i.e. if there are new users of that information and
need it to be aligned to cacheinfo which I think is highly unlikely).
--
Regards,
Sudeep
prev parent reply other threads:[~2023-03-20 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 7:53 Song Shuai
2023-03-15 18:29 ` Conor Dooley
2023-03-16 9:29 ` Sudeep Holla
2023-03-16 10:30 ` Song Shuai
2023-03-16 14:50 ` Sudeep Holla
2023-03-20 6:20 ` Song Shuai
2023-03-20 7:20 ` Sudeep Holla [this message]
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=20230320072029.j6wsdpmmq7gmlvhg@bogus \
--to=sudeep.holla@arm.com \
--cc=Pierre.Gondois@arm.com \
--cc=conor.dooley@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=ionela.voinescu@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=suagrfillet@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
all inboxes | Powered by JetHome®