From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>, xen-devel@lists.xenproject.org
Cc: Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v2 3/3] xen: prevent access to HPET from Dom0
Date: Tue, 20 Jan 2015 18:35:18 +0000 [thread overview]
Message-ID: <54BE9FE6.8010001@citrix.com> (raw)
In-Reply-To: <1421773534-15752-4-git-send-email-roger.pau@citrix.com>
On 20/01/15 17:05, Roger Pau Monne wrote:
> Prevent Dom0 from accessing HPET MMIO region by adding the HPET mfn to the
> list of read-only memory regions.
>
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> Cc: Jan Beulich <jbeulich@suse.com>
> Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Please introduce a command line parameter to control this, but
defaulting to read-only is perfectly fine.
I can well imagine that there are some bits of firmware around which
reuse the other 3/4 of the HPET page, and users with such hardware will
need a workaround. Perhaps a boolean parameter named "ro_hpet" ?
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-01-20 19:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 17:05 [PATCH v2 0/3] xen/pvh: prevent Dom0 from accessing reserved MMIO regions Roger Pau Monne
2015-01-20 17:05 ` [PATCH v2 1/3] xen: allow set_mmio_p2m_entry to specify access type Roger Pau Monne
2015-01-21 11:10 ` Jan Beulich
2015-01-20 17:05 ` [PATCH v2 2/3] xen/pvh: check permissions when adding MMIO regions Roger Pau Monne
2015-01-20 18:19 ` Andrew Cooper
2015-01-21 10:08 ` Roger Pau Monné
2015-01-21 13:02 ` Andrew Cooper
2015-01-22 15:24 ` Tim Deegan
2015-01-21 11:14 ` Jan Beulich
2015-01-20 17:05 ` [PATCH v2 3/3] xen: prevent access to HPET from Dom0 Roger Pau Monne
2015-01-20 18:35 ` Andrew Cooper [this message]
2015-01-21 10:09 ` Roger Pau Monné
2015-01-21 11:08 ` Jan Beulich
2015-01-21 11:18 ` Jan Beulich
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=54BE9FE6.8010001@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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 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.