qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] KQEMU: userspace updates of descriptor tables
Date: Tue, 03 Jun 2008 16:50:44 +0200	[thread overview]
Message-ID: <48455A44.6000404@siemens.com> (raw)

Hi,

(my) question of the day: What happens to the KQEMU's shadow GDT and LDT
if the guest modifies their content (and not their locations) while QEMU
is running in emulator mode in userspace? I just enforced dt_changed=1
in update_dt_cache(), and this took me a few steps further in the
bring-up of our special guest OS under KQEMU.

In theory, this requires some flag in the kqemu_cpu_state to signal such
events down on KQEMU_EXEC - given userspace keeps track of all changes
already. Is there such a bit? Haven't looked into that details yet.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

                 reply	other threads:[~2008-06-03 14:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=48455A44.6000404@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.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).