Managing device access using an address hint

US9575787B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9575787-B2
Application numberUS-201213483744-A
CountryUS
Kind codeB2
Filing dateMay 30, 2012
Priority dateMay 30, 2012
Publication dateFeb 21, 2017
Grant dateFeb 21, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Methods and systems for managing requests for access to devices managed by a hypervisor in virtualized computing environment. A hypervisor receives a request for access to a device from a guest. The hypervisor provides an address hint associated with the device to the guest and an association between the address hint and the device is stored in a reference table. Upon receipt of a subsequent request from the guest including the address hint, the hypervisor performs a look-up in the reference table based on the address hint to identify the device and establishes access to the device by the guest.

First claim

Opening claim text (preview).

What is claimed is: 1. A method, comprising: maintaining a reference table comprising a first set of entries relating to a first plurality of performance sensitive devices and a second set of entries relating to a second plurality of non-performance sensitive devices, wherein each of the first set of entries and the second set of entries comprises a devices identifier, a device address, and an address hint, and wherein the first set of entries comprise address hints represented by index values, and wherein the second set of entries comprise address hints represented by non-index values; receiving, by a processing devices executing a hypervisor from a guest, a first request for access to a devices, wherein the first request comprises a devices address; retrieving, from the reference table, and address hint represented by an index value associated with the device, wherein the device is identified as a performance sensitive device; transmitting, by the processing device, the address hint associated with the performance sensitive device to the guest; receiving, from the guest, a second request for access to the performance sensitive device, wherein the second request comprises the address hint; performing a first look-up in the reference table in view of the address hint represented by the index value to identify the performance sensitive device; and establishing, by the processing devices, access to the performance sensitive device in view of identifying the performance sensitive device in the first look-up. 2. The method of claim 1 , further comprising: in response to a failure of the first look-up, performance a second look-up in the reference table in view of the device address to identify the performance sensitive device, wherein the device address is provided with the second request. 3. The method of claim 1 , further comprising discarding the reference table during migration of the guest from the hypervisor to a new hypervisor. 4. The method of claim 2 , further comprising verifying the device address provided with the second request matches the device address associated with the address hint in the reference table. 5. The method of claim 1 , further comprising: transmitting, by the processing device, and updated address hint associated with the performance sensitive device to the guest in response to the second request; receiving, by the processing device from the guest, a third request for access to the performance sensitive device, wherein the third request comprises the updated address hint; performing a third look-up in the reference table in view of the updated address hint to identify the performance sensitive device; and establishing, by the processing device, access to the device in view of identifying the performance sensitive device in the third look-up. 6. The method of claim 1 , wherein the performance sensitive device comprises a high-speed device. 7. The method of claim 1 , wherein at least one of the non-performance sensitive devices comprises a low-speed device. 8. The method of claim 1 , further comprising storing the reference table prior to receiving the first request for access to the device. 9. The method of claim 1 , further comprising: generating, by the processing device, in response to receiving the first request for access, the address hint associated with the performance sensitive device; and storing, by the processing device, an associated between the address hint and the performance sensitive device in the reference table. 10. A non-transitory computer readable storage medium comprising instructions that, upon executed by a processing device, cause the processing device to: maintain a reference table comprising a first set of entries relating to a first plurality of performance sensitive devices and a second set of entries relating to a second plurality of non-performance related devices, wherein each of the first set of entries and the second set of entries comprises a device identifier, a device address, and an address hint, and wherein the first set of entries comprise address hints represented by index values, and wherein the second set of entries comprise address hints represented by non-index values; receive, by the processing device executing a hypervisor from a guest, a first request for access to a device, wherein the first request comprises a device address; retrieve, from the reference table, an address hint represented by an index value associated with the device, wherein the device is identified as a performance sensitive device; transmit, by the processing device, the address hint associated with the performance sensitive device to the guest; receive, from the guest, a second request for access to the performance sensitive device, wherein the second request comprises the address hint; perform a first look-up in the reference table in view of the address hint represented by the index value to identify the performance sensitive device; and establish, by the processing device access to the performance sensitive device in view of identifying the performance sensitive device in the first look-up. 11. The non-transitory computer readable storage medium of claim 10 , the processing device to: in response to a failure of the look-up, perform a second look-up in the reference table in view of the device address to identify the performance sensitive device, wherein the device address is provided with the second request. 12. The non-transitory computer readable storage medium of claim 10 , the processing device to discard the reference table during migration of the guest from the hypervisor to a new hypervisor. 13. The non-transitory computer readable storage medium of claim 11 , the processing device to verify the device address provided with the second request matches the device address associated with the address hint in the reference table. 14. The non-transitory computer readable storage medium of claim 10 , the processing device to: transmit, by the hypervisor, an updated address hint associated with the performance sensitive device to the guest in response to the second request; receive, from the guest, a third request for access to the performance sensitive device, wherein the third request comprises the updated address hint; perform a third look-up in the reference table in view of the updated address hint to identify the performance sensitive device; and establish, by the hypervisor, access to the device in view of identifying the performance sensitive device in the third look-up. 15. The non-transitory computer readable storage medium of claim 10 , wherein the performance sensitive device comprises a high-speed device. 16. The non-transitory computer readable storage medium of claim 10 , wherein at least one of the non-performance sensitive devices comprises a low speed device. 17. The non-transitory computer readable storage medium of claim 10 , the processing device to store the reference table prior to receiving the first request for access to the device. 18. The non-transitory computer readable storage medium of claim 10 , the processing device to: generated, by the hypervisor, in response to receiving the first request for the access, the address hint associated with the performance sensitive device; and store, by the hypervisor, an association between the address hint and the performance sensitive device in the reference table. 19. A computer system comprising: a memory to store a reference table; and a processing device, operatively coupled to the

Assignees

Inventors

Classifications

  • Hypervisor-specific management and integration aspects · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9575787B2 cover?
Methods and systems for managing requests for access to devices managed by a hypervisor in virtualized computing environment. A hypervisor receives a request for access to a device from a guest. The hypervisor provides an address hint associated with the device to the guest and an association between the address hint and the device is stored in a reference table. Upon receipt of a subsequent re…
Who is the assignee on this patent?
Tsirkin Michael, Kivity Avi, Red Hat Israel Ltd
What technology area does this patent fall under?
Primary CPC classification G06F9/45558. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Feb 21 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).