From: xen@bugs.xenproject.org
To: George Dunlap <George.Dunlap@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Processed: Re: [PATCH] Don't track all memory when enabling log dirty to track vram
Date: Mon, 10 Feb 2014 16:30:02 +0000 [thread overview]
Message-ID: <control-reply-1392049802.617@bugs.xenproject.org> (raw)
In-Reply-To: <CAFLBxZYrQf6w3N_uz4=6eEyKL_rU6EcDoKSD90ASSUt1jOLBkw@mail.gmail.com>
Processing commands for xen@bugs.xenproject.org:
> create ^
Created new bug #38 rooted at `<1392012840-22555-1-git-send-email-yang.z.zhang@intel.com>'
Title: `Re: [Xen-devel] [PATCH] Don't track all memory when enabling log dirty to track vram'
> title it HAP dirty vram tracking breaks pass-through
Set title for #38 to `HAP dirty vram tracking breaks pass-through'
> thanks
Finished processing.
Modified/created Bugs:
- 38: http://bugs.xenproject.org/xen/bug/38 (new)
---
Xen Hypervisor Bug Tracker
See http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for information on reporting bugs
Contact xen-bugs-owner@bugs.xenproject.org with any infrastructure issues
prev parent reply other threads:[~2014-02-10 16:30 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 6:14 [PATCH] Don't track all memory when enabling log dirty to track vram Yang Zhang
2014-02-10 8:03 ` Tim Deegan
2014-02-10 8:15 ` Zhang, Yang Z
2014-02-11 9:02 ` Tim Deegan
2014-02-11 10:59 ` George Dunlap
2014-02-11 11:55 ` Tim Deegan
2014-02-11 12:57 ` Jan Beulich
2014-02-11 15:55 ` George Dunlap
2014-02-12 0:53 ` Zhang, Yang Z
2014-02-13 15:46 ` George Dunlap
2014-02-13 15:55 ` Jan Beulich
2014-02-13 16:20 ` Tim Deegan
2014-02-13 16:25 ` George Dunlap
2014-02-13 16:45 ` Processed: " xen
2014-02-17 10:18 ` Jan Beulich
2014-02-17 12:23 ` George Dunlap
2014-02-17 12:37 ` Jan Beulich
2014-02-17 14:51 ` George Dunlap
2014-02-17 15:05 ` Jan Beulich
2014-02-18 3:14 ` Zhang, Yang Z
2014-02-18 10:26 ` George Dunlap
2014-02-19 1:28 ` Zhang, Yang Z
2014-02-19 8:55 ` Jan Beulich
2014-02-19 11:03 ` George Dunlap
2014-02-19 11:13 ` Jan Beulich
2014-02-19 11:17 ` George Dunlap
2014-02-17 15:00 ` Jan Beulich
2014-02-18 3:25 ` Zhang, Yang Z
2014-02-18 8:45 ` Jan Beulich
2014-02-18 11:46 ` Jan Beulich
2014-02-18 15:28 ` Jan Beulich
2014-02-19 6:40 ` Xu, Dongxiao
2014-02-19 1:17 ` Zhang, Yang Z
2014-02-19 8:50 ` Jan Beulich
2014-02-18 8:30 ` Jan Beulich
2014-05-19 7:48 ` Zhang, Yang Z
2014-05-19 9:03 ` Jan Beulich
2014-05-20 3:09 ` Zhang, Yang Z
2014-05-20 7:17 ` Jan Beulich
2014-05-19 13:27 ` George Dunlap
2014-05-19 13:50 ` Jan Beulich
2014-05-19 13:59 ` George Dunlap
2014-05-19 14:19 ` Jan Beulich
2014-05-20 3:13 ` Zhang, Yang Z
2014-05-20 7:20 ` Jan Beulich
2014-05-20 10:12 ` George Dunlap
2014-05-20 10:46 ` Jan Beulich
2014-05-21 1:02 ` Zhang, Yang Z
2014-05-21 7:49 ` Jan Beulich
2014-05-21 8:37 ` Zhang, Yang Z
2014-05-21 9:58 ` Jan Beulich
2014-05-23 6:42 ` Jan Beulich
2014-05-26 8:16 ` Zhang, Yang Z
2014-05-26 9:04 ` Jan Beulich
2014-05-31 1:26 ` Nakajima, Jun
2014-06-02 6:55 ` Jan Beulich
2014-06-02 14:06 ` George Dunlap
2014-06-02 14:27 ` Jan Beulich
2014-06-02 15:03 ` George Dunlap
2014-02-10 10:42 ` Andrew Cooper
2014-02-10 16:13 ` George Dunlap
2014-02-10 16:30 ` xen [this message]
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=control-reply-1392049802.617@bugs.xenproject.org \
--to=xen@bugs.xenproject.org \
--cc=George.Dunlap@eu.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).