From: Xiongzi Ge <gexxx132@umn.edu>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] The first function called after migration for a block device
Date: Mon, 30 Jun 2014 10:47:27 -0400 [thread overview]
Message-ID: <CACtCCo-PB1CKaJYVs2+VV6Km6u1seRZPvLPtPC069QT4FjwO=w@mail.gmail.com> (raw)
In-Reply-To: <53B175C9.3070806@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
Hi,
I mean this function will be called after migration to do something for the
block device. I tried and debugged the qemu code. (like you have a qcow2
format device. This function will be called. We can put anything we want
here. We can reopen a new device. We have a new format block device which
has a cache created by myself. I can modify and control the cache after
migration. Do you have any suggestions? Thanks. )
On Mon, Jun 30, 2014 at 10:35 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> Il 30/06/2014 16:03, Xiongzi Ge ha scritto:
>
> I tried. It invalidated the cache of the block device after migration.
>>
>
> It didn't invalidate anything in the guest, and there's *NO WAY*
> absolutely for QEMU to influence the cache in the guest.
>
> Again: all you can do is use O_DIRECT in the guest.
>
>
> So, here, we can use a new cache for the block device after migration.
>>
>
> I don't understand what you mean.
>
>
> Is it right? I can implement a simple block driver in block/ directory.
>>
>
> Probably not.
>
> Paolo
>
[-- Attachment #2: Type: text/html, Size: 1874 bytes --]
next prev parent reply other threads:[~2014-06-30 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 19:41 [Qemu-devel] The first function called after migration for a block device Xiongzi Ge
2014-06-27 21:49 ` Paolo Bonzini
2014-06-27 22:54 ` Xiongzi Ge
2014-06-30 10:48 ` Paolo Bonzini
2014-06-30 14:03 ` Xiongzi Ge
2014-06-30 14:35 ` Paolo Bonzini
2014-06-30 14:47 ` Xiongzi Ge [this message]
2014-06-30 15:13 ` Paolo Bonzini
2014-06-30 15:17 ` Xiongzi Ge
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='CACtCCo-PB1CKaJYVs2+VV6Km6u1seRZPvLPtPC069QT4FjwO=w@mail.gmail.com' \
--to=gexxx132@umn.edu \
--cc=pbonzini@redhat.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 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.