From: Don Dutile <ddutile@redhat.com>
To: Ky Srinivasan <ksrinivasan@novell.com>
Cc: xen-devel@lists.xensource.com, Don Dutile <ddutile@redhat.com>
Subject: Re: swiotlb
Date: Thu, 13 Apr 2006 21:51:28 -0400 [thread overview]
Message-ID: <443F0020.6060300@redhat.com> (raw)
In-Reply-To: <443E7C63.E57C.0030.0@novell.com>
Ky,
You are correct. I received this as a bugzilla on FC-5. Testing a
solution now (replacing copy_to_user w/copy_to_user_inatomic).
The other problem with the call to copy_to_user is that a kmap_atomic()
is done just before it as well, and the thread can't be blocked before
the kunmap_atomic() is invoked (after the copy_to_user()).
Unfortunately, tomorrow is company holiday, so I won't complete the
testing until Monday; need to get more memory to force swiotlb's
sync_single() to do the copy (due to bounce IO).
- Don
Ky Srinivasan wrote:
> Given that the function __sync_single() can be called in an interrupt
> context, why do we call a potentially blocking function
> (__copy_to_user) from within this function?
>
> Regards,
>
> K. Y
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-04-14 1:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 20:29 swiotlb Ky Srinivasan
2006-04-14 1:51 ` Don Dutile [this message]
2006-04-14 13:34 ` swiotlb Ky Srinivasan
2006-04-14 6:50 ` swiotlb Keir Fraser
2006-04-14 13:36 ` swiotlb Ky Srinivasan
-- strict thread matches above, loose matches on Subject: below --
2007-04-05 14:23 Swiotlb Kieran Mansley
2007-04-05 15:10 ` Swiotlb Keir Fraser
2007-04-10 8:41 ` Swiotlb Kieran Mansley
2007-04-10 8:58 ` Swiotlb Muli Ben-Yehuda
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=443F0020.6060300@redhat.com \
--to=ddutile@redhat.com \
--cc=ksrinivasan@novell.com \
--cc=xen-devel@lists.xensource.com \
/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.