From: "tan.shaopeng@fujitsu.com" <tan.shaopeng@fujitsu.com>
To: 'James Morse' <james.morse@arm.com>
Cc: "'catalin.marinas@arm.com'" <catalin.marinas@arm.com>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
"misono.tomohiro@fujitsu.com" <misono.tomohiro@fujitsu.com>
Subject: RE: About resctrl code rebase
Date: Fri, 3 Dec 2021 07:58:28 +0000 [thread overview]
Message-ID: <TYAPR01MB6330606C7AA6A633806D90118B6A9@TYAPR01MB6330.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <TYAPR01MB6330F3B97D23A214FB4DA7C48B619@TYAPR01MB6330.jpnprd01.prod.outlook.com>
Hi James
> > On 01/09/2021 09:35, tan.shaopeng@fujitsu.com wrote:
> > >> As you known, Fujitsu is implementing a feature that add A64FX's
> > >> cache control function into resctrl.
> >
> > >> Fujitsu will implement this feature base on your rebased code. I
> > >> think the commit of refactoring arch/x86 implementation of resctrl
> > >> has been merged into the x86/cache branch.
> > >> https://lore.kernel.org/lkml/162871088112.395.12879267279872673224.
> > >> ti
> > >> p-bot2@tip-bot2/
> >
> > I'm afraid this was only a small part of it.
> >
> > I've also posted the next series here:
> > https://lore.kernel.org/lkml/20210729223610.29373-1-james.morse@arm.co
> > m
> > /
> >
> > and there are a couple more after that.
>
> When will you post patches v3? And are there any other patches after this?
>
> > >> I would like to know whether you have rebased these codes that move
> > >> the common parts of multiple architectures to somewhere.
> > >> And where is the rebase code?
> > >> In addition, when will you release the latest MPAM patch?
> >
> > I will keep posting 'the next part' of the x86 changes once the
> > earlier part is reviewed.
> > (please help!)
> >
> > I can't push the latest branch until the ACPI spec is published, but I
> > hope that will happen this month.
>
> Could you tell me when you are planning to push the rebase code?
> Is there anything I can do for you?
I look forward to hearing from you.
Best regards,
Tan shaopeng
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-03 8:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 8:35 About resctrl code rebase tan.shaopeng
2021-09-01 17:04 ` James Morse
2021-09-01 17:04 ` James Morse
2021-09-06 6:19 ` tan.shaopeng
2021-09-06 6:19 ` tan.shaopeng
2021-11-24 11:17 ` tan.shaopeng
2021-11-24 11:17 ` tan.shaopeng
2021-12-03 7:58 ` tan.shaopeng [this message]
2021-12-06 20:35 ` Rob Herring
2021-12-08 11:56 ` tan.shaopeng
2022-01-04 9:53 ` tan.shaopeng
-- strict thread matches above, loose matches on Subject: below --
2021-08-19 5:14 tan.shaopeng
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=TYAPR01MB6330606C7AA6A633806D90118B6A9@TYAPR01MB6330.jpnprd01.prod.outlook.com \
--to=tan.shaopeng@fujitsu.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=misono.tomohiro@fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.