From: Paul Durrant <Paul.Durrant@citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>, Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>
Subject: Re: [PATCH 6/8] viridian: separate time related enlightenment implementations...
Date: Tue, 30 Oct 2018 17:08:09 +0000 [thread overview]
Message-ID: <e827bf8c3e484ea4b33c965ae3771c81@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20181030170320.6jie6ta6uoece7nr@mac.citrite.net>
> -----Original Message-----
> From: Roger Pau Monne
> Sent: 30 October 2018 17:03
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: xen-devel@lists.xenproject.org; Andrew Cooper
> <Andrew.Cooper3@citrix.com>; Wei Liu <wei.liu2@citrix.com>; Jan Beulich
> <jbeulich@suse.com>
> Subject: Re: [Xen-devel] [PATCH 6/8] viridian: separate time related
> enlightenment implementations...
>
> On Mon, Oct 29, 2018 at 06:02:09PM +0000, Paul Durrant wrote:
> > @@ -154,6 +145,14 @@ viridian_hypercall(struct cpu_user_regs *regs);
> > void viridian_time_ref_count_freeze(struct domain *d);
> > void viridian_time_ref_count_thaw(struct domain *d);
> >
> > +int viridian_time_wrmsr(struct vcpu *v, uint32_t idx, uint64_t val);
> > +int viridian_time_rdmsr(const struct vcpu *v, uint32_t idx, uint64_t
> *val);
> > +
> > +void viridian_time_save_domain_ctxt(
> > + const struct domain *d, struct hvm_viridian_domain_context *ctxt);
> > +void viridian_time_load_domain_ctxt(
> > + struct domain *d, struct hvm_viridian_domain_context *ctxt);
>
> Can ctxt be constifyed in the load case?
I guess it could be, yes.
Paul
>
> Thanks, Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-10-30 17:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 18:02 [PATCH 0/8] viridian cleanup Paul Durrant
2018-10-29 18:02 ` [PATCH 1/8] viridian: move the code into its own sub-directory Paul Durrant
2018-10-30 9:25 ` Jan Beulich
2018-10-31 10:17 ` Jan Beulich
2018-10-31 10:30 ` Paul Durrant
2018-10-29 18:02 ` [PATCH 1/2] x86/mm/p2m: don't needlessly limit MMIO mapping order to 4k Paul Durrant
2018-10-29 18:03 ` Paul Durrant
2018-10-29 18:02 ` [PATCH 2/2] iommu / p2m: add a page_order parameter to iommu_map/unmap_page() Paul Durrant
2018-10-29 18:03 ` Paul Durrant
2018-10-29 18:02 ` [PATCH 2/8] viridian: remove MSR perf counters Paul Durrant
2018-10-30 16:25 ` Roger Pau Monné
2018-10-29 18:02 ` [PATCH 3/8] viridian: remove comments referencing section number in the spec Paul Durrant
2018-10-30 16:34 ` Roger Pau Monné
2018-10-30 17:07 ` Paul Durrant
2018-10-29 18:02 ` [PATCH 4/8] viridian: remove duplicate union types Paul Durrant
2018-10-30 16:40 ` Roger Pau Monné
2018-10-30 17:03 ` Paul Durrant
2018-10-31 8:44 ` Roger Pau Monné
2018-10-29 18:02 ` [PATCH 5/8] viridian: separate interrupt related enlightenment implementations Paul Durrant
2018-10-30 16:52 ` Roger Pau Monné
2018-10-30 17:06 ` Paul Durrant
2018-10-29 18:02 ` [PATCH 6/8] viridian: separate time " Paul Durrant
2018-10-30 17:03 ` Roger Pau Monné
2018-10-30 17:08 ` Paul Durrant [this message]
2018-10-29 18:02 ` [PATCH 7/8] viridian: define type for the 'virtual VP assist page' Paul Durrant
2018-10-30 17:08 ` Roger Pau Monné
2018-10-30 17:11 ` Paul Durrant
2018-10-31 8:53 ` Roger Pau Monné
2018-10-31 9:27 ` Paul Durrant
2018-10-31 9:41 ` Jan Beulich
2018-10-31 10:01 ` Paul Durrant
2018-10-31 10:16 ` Jan Beulich
2018-10-29 18:02 ` [PATCH 8/8] viridian: introduce struct viridian_page Paul Durrant
2018-10-30 17:17 ` Roger Pau Monné
2018-10-30 17:25 ` Paul Durrant
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=e827bf8c3e484ea4b33c965ae3771c81@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@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 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).