From: "Michael S. Tsirkin" <mst@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, marcel.apfelbaum@gmail.com
Subject: Re: [PATCH 4/4] pcie: add trace-point for power indicator transitions
Date: Wed, 1 Mar 2023 15:53:13 -0500 [thread overview]
Message-ID: <20230301155249-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <d6ea345b-d3d1-0dfa-20cb-fb328900086a@yandex-team.ru>
On Tue, Feb 07, 2023 at 01:39:03PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Thanks for reviewing!
>
> On 05.02.23 13:56, Philippe Mathieu-Daudé wrote:
> > On 4/2/23 18:47, Vladimir Sementsov-Ogievskiy wrote:
> > > Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
> > > ---
> > > hw/pci/pcie.c | 20 ++++++++++++++++++++
> > > hw/pci/trace-events | 3 +++
> > > 2 files changed, 23 insertions(+)
> >
> > > +static const char *pcie_sltctl_pic_str(uint16_t sltctl)
> > > +{
> > > + switch (sltctl & PCI_EXP_SLTCTL_PIC) {
> > > + case PCI_EXP_SLTCTL_PWR_IND_ON:
> > > + return "on";
> > > + case PCI_EXP_SLTCTL_PWR_IND_BLINK:
> > > + return "blink";
> > > + case PCI_EXP_SLTCTL_PWR_IND_OFF:
> > > + return "off";
> > > + default:
> > > + return "?";
> >
> > Maybe "illegal"?
>
> I just was unsure about it.
>
> For SHPC, 0 is correct, and means that this command don't change the led state.
>
> But with PCI-e hotplug we don't have such commands but change the led directly, so it must be one of "on"/"blink"/"off", and zero is really wrong, right?
>
>
> Also, I'm now looking at /* TODO: send event to monitor */ in shpc code, and working on it. So, I think, I'll soon send patches with such event for both SHPC and PCI-e, and probably that trace point becomes not needed.
I think it's ok to queue as is, change it with a patch on top.
> >
> > Otherwise:
> >
> > Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> >
> > > + }
> > > +}
> >
>
> --
> Best regards,
> Vladimir
next prev parent reply other threads:[~2023-03-01 20:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 17:47 [PATCH 0/4] pcie: cleanup code and add trace point Vladimir Sementsov-Ogievskiy
2023-02-04 17:47 ` [PATCH 3/4] pcie: drop unused PCIExpressIndicator Vladimir Sementsov-Ogievskiy
2023-02-07 11:57 ` Philippe Mathieu-Daudé
2023-02-04 17:47 ` [PATCH 4/4] pcie: add trace-poing for power indicator transitions Vladimir Sementsov-Ogievskiy
[not found] ` <20230204174758.234951-3-vsementsov@yandex-team.ru>
2023-02-05 10:53 ` [PATCH 2/4] pcie_regs: drop duplicated indicator value macros Philippe Mathieu-Daudé
[not found] ` <20230204174758.234951-2-vsementsov@yandex-team.ru>
2023-02-05 10:54 ` [PATCH 1/4] pcie: pcie_cap_slot_write_config(): use correct macro Philippe Mathieu-Daudé
[not found] ` <20230204174758.234951-6-vsementsov@yandex-team.ru>
2023-02-05 10:56 ` [PATCH 4/4] pcie: add trace-point for power indicator transitions Philippe Mathieu-Daudé
2023-02-07 10:39 ` Vladimir Sementsov-Ogievskiy
2023-03-01 20:53 ` Michael S. Tsirkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-07 12:09 [PATCH 0/4] pcie: cleanup code and add trace point Vladimir Sementsov-Ogievskiy
2023-02-07 12:09 ` [PATCH 4/4] pcie: add trace-point for power indicator transitions Vladimir Sementsov-Ogievskiy
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=20230301155249-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
/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.