From: Avi Kivity <avi@redhat.com>
To: Laurent Vivier <Laurent.Vivier@bull.net>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: Device Assignment with VT-d
Date: Tue, 16 Sep 2008 11:18:30 -0700 [thread overview]
Message-ID: <48CFF876.8000801@redhat.com> (raw)
In-Reply-To: <1221568935.4172.22.camel@frecb07144>
Laurent Vivier wrote:
>> @@ -1147,6 +1157,9 @@ int kvm_dev_ioctl_check_extension(long ext)
>> case KVM_CAP_PV_MMU:
>> r = !tdp_enabled;
>> break;
>> + case KVM_CAP_IOMMU:
>> + r = intel_iommu_found();
>> + break;
>>
>
> Must depend on CONFIG_DMAR too
>
Rather, intel_iommu_found() should be defined (and return zero) if
!CONFIG_DMAR.
(what's a dmar?)
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-09-16 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080916005853.7876D250DB2@il.qumranet.com>
2008-09-16 12:42 ` [PATCH] KVM: Device Assignment with VT-d Laurent Vivier
2008-09-16 18:18 ` Avi Kivity [this message]
2008-09-17 3:56 ` Muli Ben-Yehuda
2008-08-22 7:10 VT-d support for device assignment Amit Shah
2008-08-22 7:10 ` [PATCH] VT-d: changes to support KVM Amit Shah
2008-08-22 7:10 ` [PATCH] KVM: Device Assignment with VT-d Amit Shah
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=48CFF876.8000801@redhat.com \
--to=avi@redhat.com \
--cc=Laurent.Vivier@bull.net \
--cc=kvm@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.