WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Address check restriction

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Address check restriction
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Thu, 19 Oct 2006 15:37:37 -0400
Delivery-date: Thu, 19 Oct 2006 12:38:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Keir,

   I'd like to restrict the address check in the code snipped below so
that addresses in the range 0xFED4 0000 to 0xFED4 5000 do not end up in
the domain_crash() function. I have a virtual device (qemu device model)
that uses addresses in this range. Can I just open up that window with a
check like this or can the window even be further open onto higher
addresses?

    if ( !hvm_apic_support(d) && 
         (((gpa >= 0xFEC00000) && (gpa < FED40000)) ||
           (gpa >= 0xFED45000)  ))


The device is a TPM TIS interface. Specs at:

https://www.trustedcomputinggroup.org/groups/pc_client/TCG_PCClientTPMSpecification_1-20_1-00_FINAL.pdf

Page 27 shows the address range.


from xen/arch/x86/mm/shadow/multi.c:

 mmio:
    perfc_incrc(shadow_fault_mmio);
    if ( !hvm_apic_support(d) && (gpa >= 0xFEC00000) )
    {
        /* Need to deal with these disabled-APIC accesses, as
         * handle_mmio() apparently does not currently do that. */
        /* TJD: What about it, then?   For now, I'm turning this BUG()
         * into a domain_crash() since we don't want to kill Xen. */
        SHADOW_ERROR("disabled-APIC access: not supported\n.");
        domain_crash(d);
    }



  Stefan



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>