From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH] qemu-kvm: Flush icache after dma operations for ia64
Date: Tue, 26 May 2009 12:30:26 +0000 [thread overview]
Message-ID: <4A1BE0E2.3090306@redhat.com> (raw)
In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC236B1935F@pdsmsx503.ccr.corp.intel.com>
Jes Sorensen wrote:
> Ok,
>
> Trying once more. After spending a couple of hours trying to follow
> the QEMU dma codeflow, I have convinced myself Avi is right and those
> two functions don't need to do the flushing as they all end up calling
> dma_bdrv_cb() which calls dma_brdv_unmap(). I have added a couple
> comments to the code, which will hopefully save the next person the
> 'pleasure' of trying to figure out this too.
>
It looks right to me. Xiantao?
> access_len -= l;
> - }
> + }
> + dma_flush_range((unsigned long)buffer,
> + (unsigned long)buffer + flush_len);
> }
>
Detab your code, please.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Jes Sorensen <jes@sgi.com>
Cc: "Zhang, Xiantao" <xiantao.zhang@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>,
Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [PATCH] qemu-kvm: Flush icache after dma operations for ia64
Date: Tue, 26 May 2009 15:30:26 +0300 [thread overview]
Message-ID: <4A1BE0E2.3090306@redhat.com> (raw)
In-Reply-To: <4A1A9951.5030408@sgi.com>
Jes Sorensen wrote:
> Ok,
>
> Trying once more. After spending a couple of hours trying to follow
> the QEMU dma codeflow, I have convinced myself Avi is right and those
> two functions don't need to do the flushing as they all end up calling
> dma_bdrv_cb() which calls dma_brdv_unmap(). I have added a couple
> comments to the code, which will hopefully save the next person the
> 'pleasure' of trying to figure out this too.
>
It looks right to me. Xiantao?
> access_len -= l;
> - }
> + }
> + dma_flush_range((unsigned long)buffer,
> + (unsigned long)buffer + flush_len);
> }
>
Detab your code, please.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-05-26 12:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 10:20 [PATCH] qemu-kvm: Flush icache after dma operations for ia64 Zhang, Xiantao
2009-05-11 10:20 ` Zhang, Xiantao
2009-05-11 11:11 ` Avi Kivity
2009-05-11 11:11 ` Avi Kivity
2009-05-25 10:55 ` Jes Sorensen
2009-05-25 10:55 ` Jes Sorensen
2009-05-25 10:56 ` Jes Sorensen
2009-05-25 10:56 ` Jes Sorensen
2009-05-25 11:25 ` Avi Kivity
2009-05-25 11:25 ` Avi Kivity
2009-05-25 13:12 ` Jes Sorensen
2009-05-25 13:12 ` Jes Sorensen
2009-05-26 12:30 ` Avi Kivity [this message]
2009-05-26 12:30 ` Avi Kivity
2009-06-01 5:40 ` Zhang, Xiantao
2009-06-01 5:40 ` Zhang, Xiantao
2009-06-01 7:45 ` Avi Kivity
2009-06-01 7:45 ` Avi Kivity
2009-06-02 10:56 ` Jes Sorensen
2009-06-02 10:56 ` Jes Sorensen
2009-06-02 15:20 ` Zhang, Xiantao
2009-06-02 15:20 ` Zhang, Xiantao
2009-06-04 13:09 ` Jes Sorensen
2009-06-04 13:09 ` Jes Sorensen
2009-06-05 1:38 ` Zhang, Xiantao
2009-06-05 1:38 ` Zhang, Xiantao
2009-06-05 11:13 ` Jes Sorensen
2009-06-05 11:13 ` Jes Sorensen
2009-06-07 6:28 ` Avi Kivity
2009-06-07 6:28 ` Avi Kivity
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=4A1BE0E2.3090306@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ia64@vger.kernel.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.