From: Petre Ovidiu PIRCALABU <ppircalabu@bitdefender.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: "tamas@tklengyel.com" <tamas@tklengyel.com>,
"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
"rcojocaru@bitdefender.com" <rcojocaru@bitdefender.com>,
"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
"jbeulich@suse.com" <jbeulich@suse.com>
Subject: Re: write_ctrlreg event masking
Date: Fri, 16 Jun 2017 14:09:32 +0000 [thread overview]
Message-ID: <1497622172.5361.1.camel@bitdefender.com> (raw)
In-Reply-To: <1496137567-6574-1-git-send-email-ppircalabu@bitdefender.com>
Hello,
Any comments for this series?
Thanks,
Petre
On Ma, 2017-05-30 at 12:46 +0300, Petre Pircalabu wrote:
> This patchset enables masking the reception of write_ctrlreg events
> depending
> on the value of certain bits in that register.
> The most representative example is filtering out events when the
> CR4.PGE
> bit is being flipped (global TLB flushes)
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
>
> ________________________
> This email was scanned by Bitdefender
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-16 14:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 13:41 write_ctrlreg event masking Petre Pircalabu
2017-05-26 13:41 ` [PATCH 1/2] x86/monitor: add masking support for write_ctrlreg events Petre Pircalabu
2017-05-29 15:01 ` Jan Beulich
2017-05-30 9:38 ` Petre PIRCALABU
2017-05-26 13:41 ` [PATCH 2/2] xen-access: write_ctrlreg_c4 test Petre Pircalabu
2017-05-30 9:46 ` write_ctrlreg event masking Petre Pircalabu
2017-05-30 9:46 ` [PATCH v2 1/2] x86/monitor: add masking support for write_ctrlreg events Petre Pircalabu
2017-06-16 14:26 ` Tamas K Lengyel
2017-06-16 15:15 ` Jan Beulich
2017-06-16 15:28 ` Tamas K Lengyel
2017-06-16 15:33 ` Jan Beulich
2017-06-16 16:24 ` Tamas K Lengyel
2017-05-30 9:46 ` [PATCH v2 2/2] xen-access: write_ctrlreg_c4 test Petre Pircalabu
2017-06-16 14:32 ` Tamas K Lengyel
2017-06-16 15:12 ` Jan Beulich
2017-06-16 15:24 ` Tamas K Lengyel
2017-06-16 14:09 ` Petre Ovidiu PIRCALABU [this message]
2017-06-16 19:20 ` [PATCH v3 0/2] write_ctrlreg event masking Petre Pircalabu
2017-06-16 19:20 ` [PATCH v3 1/2] x86/monitor: add masking support for write_ctrlreg events Petre Pircalabu
2017-06-16 19:20 ` [PATCH v3 2/2] xen-access: write_ctrlreg_c4 test Petre Pircalabu
2017-06-16 19:45 ` Razvan Cojocaru
2017-06-19 12:24 ` [PATCH v4 0/2] write_ctrlreg event masking Petre Pircalabu
2017-06-19 12:24 ` [PATCH v4 1/2] x86/monitor: add masking support for write_ctrlreg events Petre Pircalabu
2017-06-20 12:42 ` Wei Liu
2017-06-21 13:58 ` Wei Liu
2017-06-21 14:11 ` Tamas K Lengyel
2017-06-21 14:13 ` Razvan Cojocaru
2017-06-21 14:19 ` Wei Liu
2017-06-19 12:24 ` [PATCH v4 2/2] xen-access: write_ctrlreg_c4 test Petre Pircalabu
2017-06-19 14:51 ` Tamas K Lengyel
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=1497622172.5361.1.camel@bitdefender.com \
--to=ppircalabu@bitdefender.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=rcojocaru@bitdefender.com \
--cc=tamas@tklengyel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).