From: Rui Wang <ruiv.wang@gmail.com>
To: bhelgaas@google.com
Cc: tony.luck@intel.com, chaohong.guo@intel.com,
gong.chen@linux.intel.com, rafael.j.wysocki@intel.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, Rui Wang <rui.y.wang@intel.com>
Subject: [RFC v2 0/3] I/O Hook: Method for emulating h/w events
Date: Thu, 1 Aug 2013 18:31:30 +0800 [thread overview]
Message-ID: <1375353093-3206-1-git-send-email-rui.y.wang@intel.com> (raw)
Hi Bjorn,
In this v2, I made the following changes according to your suggestion:
1) The iohook driver is now built-in so we have alot fewer exported
symbols. But we still need to export two functions because the
loadable modules need to call into the I/O Hook.
2) Non-PCI part moved from drivers/pci into drivers/misc/iohook
3) It's now platform neutral. The PCI part should now work on all
platforms. The memory mapped I/O part can be easily extened later
to non-x86 platforms by modifying their part under arch/
I tested this new version on Westmere-EX. It worked as expected.
Regards,
Rui Wang
Intel Open Source Technology Center
Rui Wang (3):
I/O Hook: core functions and Register Override
I/O Hook: kernel interface to manage the hook
I/O Hook: sysfs interface to emulate h/w events
Documentation/PCI/iohook.txt | 282 ++++++++++
arch/Kconfig | 10 +
arch/x86/boot/compressed/Makefile | 1 +
arch/x86/include/asm/io.h | 57 ++-
arch/x86/vdso/Makefile | 2 +
drivers/misc/Makefile | 1 +
drivers/misc/iohook/Makefile | 1 +
drivers/misc/iohook/iohook.c | 1025 +++++++++++++++++++++++++++++++++++++
drivers/misc/iohook/iohook.h | 6 +
drivers/pci/access.c | 66 +++
include/linux/reg_ovrd.h | 51 ++
11 files changed, 1500 insertions(+), 2 deletions(-)
create mode 100644 Documentation/PCI/iohook.txt
create mode 100644 drivers/misc/iohook/Makefile
create mode 100644 drivers/misc/iohook/iohook.c
create mode 100644 drivers/misc/iohook/iohook.h
create mode 100644 include/linux/reg_ovrd.h
--
1.7.5.4
next reply other threads:[~2013-08-01 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 10:31 Rui Wang [this message]
2013-08-01 10:31 ` [RFC v2 1/3] I/O Hook: core functions and Register Override Rui Wang
2013-08-01 10:31 ` [RFC v2 2/3] I/O Hook: kernel interface to manage the hook Rui Wang
2013-08-01 10:31 ` [RFC v2 3/3] I/O Hook: sysfs interface to emulate h/w events Rui Wang
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=1375353093-3206-1-git-send-email-rui.y.wang@intel.com \
--to=ruiv.wang@gmail.com \
--cc=bhelgaas@google.com \
--cc=chaohong.guo@intel.com \
--cc=gong.chen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rui.y.wang@intel.com \
--cc=tony.luck@intel.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).