From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xensource.com
Subject: possible code/comment mismatch in hap_enable_vram_tracking/hap_clean_vram_tracking
Date: Thu, 9 Sep 2010 15:37:46 +0200 [thread overview]
Message-ID: <20100909133746.GA15174@aepfle.de> (raw)
Hello,
the comments in hap_enable_vram_tracking() and hap_clean_vram_tracking()
say the pages will be set to read-only, but it passes p2m_ram_rw instead
of p2m_ram_ro to p2m_change_type().
Bug or feature?
Olaf
next reply other threads:[~2010-09-09 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 13:37 Olaf Hering [this message]
2010-09-09 13:48 ` possible code/comment mismatch in hap_enable_vram_tracking/hap_clean_vram_tracking Tim Deegan
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=20100909133746.GA15174@aepfle.de \
--to=olaf@aepfle.de \
--cc=xen-devel@lists.xensource.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 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.