From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: linux-input@vger.kernel.org,
Vincent Huang <vincent.huang@tw.synaptics.com>,
Lyude Paul <lyude@redhat.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jikos@kernel.org>,
Andrew Duggan <aduggan@synaptics.com>,
Hans de Goede <hdegoede@redhat.com>,
Benjamin Tissoires <btissoir@redhat.com>,
Chris Heiny <chris.heiny@synaptics.com>,
Sultan Alsawaf <sultan@kerneltoast.com>
Subject: Re: [PATCH v3 2/2] Input: synaptics - enable InterTouch for ThinkPad P1/X1E gen 2
Date: Wed, 7 Oct 2020 17:55:03 +0200 [thread overview]
Message-ID: <CAHmME9rAu0nVTGaQK84MxODuR9Ym3Q1FTyw_sVStmUTs9kmifQ@mail.gmail.com> (raw)
In-Reply-To: <20200930225046.173190-3-Jason@zx2c4.com>
Oddly, CPU usage seems exceedingly high when using the trackpoint, in
the rmi4 irq handler. Running perf-top indicates a hotspot in
i801_access calling "in (%dx),%al", which makes sense. I wonder:
is this a culprit of expensive accesses in general, which Sultan
(CC'd) has been working on? Or are we hitting something different
here? Improper IRQ masking in the i801 code?
Jason
next prev parent reply other threads:[~2020-10-07 15:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 16:36 [PATCH] Input: synaptics - enable InterTouch for ThinkPad X1E/P1 2nd gen Jason A. Donenfeld
2020-09-30 11:07 ` Jason A. Donenfeld
2020-09-30 11:24 ` [PATCH v2] " Jason A. Donenfeld
2020-09-30 16:05 ` Lyude Paul
2020-09-30 16:18 ` Jason A. Donenfeld
2020-09-30 19:55 ` Lyude Paul
2020-09-30 22:55 ` Jason A. Donenfeld
2020-09-30 22:50 ` [PATCH v3 0/2] Support trackpoint and touchpad in Thinkpad P1 gen 2 / X1E gen 2 Jason A. Donenfeld
2020-09-30 22:50 ` [PATCH v3 1/2] Input: synaptics-rmi4 - support bootloader v8 in f34v7 Jason A. Donenfeld
2020-10-05 2:50 ` Dmitry Torokhov
2020-09-30 22:50 ` [PATCH v3 2/2] Input: synaptics - enable InterTouch for ThinkPad P1/X1E gen 2 Jason A. Donenfeld
2020-10-05 2:51 ` Dmitry Torokhov
2020-10-07 15:55 ` Jason A. Donenfeld [this message]
2020-10-11 9:00 ` Jason A. Donenfeld
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=CAHmME9rAu0nVTGaQK84MxODuR9Ym3Q1FTyw_sVStmUTs9kmifQ@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=aduggan@synaptics.com \
--cc=btissoir@redhat.com \
--cc=chris.heiny@synaptics.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=sultan@kerneltoast.com \
--cc=vincent.huang@tw.synaptics.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).